FKIE_CVE-2025-12472

Vulnerability from fkie_nvd - Published: 2025-11-19 11:15 - Updated: 2026-10-18 20:10
Severity
7.1 (High) - CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/U:Red
Summary
An attacker with a Looker Developer role could manipulate a LookML project to exploit a race condition during Git directory deletion, leading to arbitrary command execution on the Looker instance. Looker-hosted and Self-hosted were found to be vulnerable. This issue has already been mitigated for Looker-hosted instances. No user action is required for these. Self-hosted instances must be upgraded as soon as possible. This vulnerability has been patched in all supported versions of Self-hosted. The versions below have all been updated to protect from this vulnerability. You can download these versions at the Looker download page https://download.looker.com/ : * 24.12.103+ * 24.18.195+ * 25.0.72+ * 25.6.60+ * 25.8.42+ * 25.10.22+
References
f45cbf4e-4146-4068-b7e1-655ffc2c548chttps://cloud.google.com/support/bulletins#gcp-2025-052
Impacted products
Vendor Product Version
To clipboard 

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "platforms": [
            "Looker-hosted"
          ],
          "product": "Looker",
          "vendor": "Google Cloud",
          "versions": [
            {
              "lessThan": "24.12.103",
              "status": "affected",
              "version": "0",
              "versionType": "date"
            },
            {
              "lessThan": "24.18.195",
              "status": "affected",
              "version": "0",
              "versionType": "date"
            },
            {
              "lessThan": "25.0.72",
              "status": "affected",
              "version": "0",
              "versionType": "date"
            },
            {
              "lessThan": "25.6.60",
              "status": "affected",
              "version": "0",
              "versionType": "date"
            },
            {
              "lessThan": "25.8.42",
              "status": "affected",
              "version": "0",
              "versionType": "date"
            },
            {
              "lessThan": "25.10.22",
              "status": "affected",
              "version": "0",
              "versionType": "date"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "platforms": [
            "Self-hosted"
          ],
          "product": "Looker",
          "vendor": "Google Cloud",
          "versions": [
            {
              "lessThan": "24.12.103",
              "status": "affected",
              "version": "0",
              "versionType": "date"
            },
            {
              "lessThan": "24.18.195",
              "status": "affected",
              "version": "0",
              "versionType": "date"
            },
            {
              "lessThan": "25.0.72",
              "status": "affected",
              "version": "0",
              "versionType": "date"
            },
            {
              "lessThan": "25.6.60",
              "status": "affected",
              "version": "0",
              "versionType": "date"
            },
            {
              "lessThan": "25.8.42",
              "status": "affected",
              "version": "0",
              "versionType": "date"
            },
            {
              "lessThan": "25.10.22",
              "status": "affected",
              "version": "0",
              "versionType": "date"
            }
          ]
        }
      ],
      "source": "f45cbf4e-4146-4068-b7e1-655ffc2c548c"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "An attacker with a Looker Developer role could manipulate a LookML project to exploit a race condition during Git directory deletion, leading to arbitrary command execution on the Looker instance.\n\n\n\nLooker-hosted and Self-hosted were found to be vulnerable.\nThis issue has already been mitigated for Looker-hosted instances.\u00a0No user action is required for these.\n\n\nSelf-hosted instances must be upgraded as soon as possible. This vulnerability has been patched in all supported versions of Self-hosted.\nThe versions below have all been updated to protect from this vulnerability. You can download these versions at the Looker download page  https://download.looker.com/ :\n  *  24.12.103+\n  *  24.18.195+\n  *  25.0.72+\n  *  25.6.60+\n  *  25.8.42+\n  *  25.10.22+"
    },
    {
      "lang": "es",
      "value": "Un atacante con un rol de desarrollador de Looker podr\u00eda manipular un proyecto LookML para explotar una condici\u00f3n de carrera durante la eliminaci\u00f3n de un directorio Git, lo que llevar\u00eda a la ejecuci\u00f3n arbitraria de comandos en la instancia de Looker.\n\nSe encontr\u00f3 que las instancias Looker-hosted y Self-hosted eran vulnerables.\nEste problema ya ha sido mitigado para las instancias Looker-hosted. No se requiere ninguna acci\u00f3n por parte del usuario para estas.\n\nLas instancias Self-hosted deben actualizarse lo antes posible. Esta vulnerabilidad ha sido parcheada en todas las versiones compatibles de Self-hosted.\nLas versiones a continuaci\u00f3n han sido todas actualizadas para proteger contra esta vulnerabilidad. Puede descargar estas versiones en la p\u00e1gina de descarga de Looker https://download.looker.com/ :\n  * 24.12.103+\n  * 24.18.195+\n  * 25.0.72+\n  * 25.6.60+\n  * 25.8.42+\n  * 25.10.22+"
    }
  ],
  "id": "CVE-2025-12472",
  "lastModified": "2026-10-18T20:10:00.110",
  "metrics": {
    "cvssMetricV40": [
      {
        "cvssData": {
          "Automatable": "NOT_DEFINED",
          "Recovery": "NOT_DEFINED",
          "Safety": "NOT_DEFINED",
          "attackComplexity": "HIGH",
          "attackRequirements": "PRESENT",
          "attackVector": "NETWORK",
          "availabilityRequirement": "NOT_DEFINED",
          "baseScore": 7.1,
          "baseSeverity": "HIGH",
          "confidentialityRequirement": "NOT_DEFINED",
          "exploitMaturity": "NOT_DEFINED",
          "integrityRequirement": "NOT_DEFINED",
          "modifiedAttackComplexity": "NOT_DEFINED",
          "modifiedAttackRequirements": "NOT_DEFINED",
          "modifiedAttackVector": "NOT_DEFINED",
          "modifiedPrivilegesRequired": "NOT_DEFINED",
          "modifiedSubAvailabilityImpact": "NOT_DEFINED",
          "modifiedSubConfidentialityImpact": "NOT_DEFINED",
          "modifiedSubIntegrityImpact": "NOT_DEFINED",
          "modifiedUserInteraction": "NOT_DEFINED",
          "modifiedVulnAvailabilityImpact": "NOT_DEFINED",
          "modifiedVulnConfidentialityImpact": "NOT_DEFINED",
          "modifiedVulnIntegrityImpact": "NOT_DEFINED",
          "privilegesRequired": "HIGH",
          "providerUrgency": "RED",
          "subAvailabilityImpact": "NONE",
          "subConfidentialityImpact": "NONE",
          "subIntegrityImpact": "NONE",
          "userInteraction": "ACTIVE",
          "valueDensity": "NOT_DEFINED",
          "vectorString": "CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Red",
          "version": "4.0",
          "vulnAvailabilityImpact": "HIGH",
          "vulnConfidentialityImpact": "HIGH",
          "vulnIntegrityImpact": "HIGH",
          "vulnerabilityResponseEffort": "NOT_DEFINED"
        },
        "source": "f45cbf4e-4146-4068-b7e1-655ffc2c548c",
        "type": "Secondary"
      }
    ],
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2025-12472",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "role": "CISA Coordinator",
          "timestamp": "2025-11-19T16:20:20.583208Z",
          "version": "2.0.3"
        }
      }
    ]
  },
  "published": "2025-11-19T11:15:44.383",
  "references": [
    {
      "source": "f45cbf4e-4146-4068-b7e1-655ffc2c548c",
      "url": "https://cloud.google.com/support/bulletins#gcp-2025-052"
    }
  ],
  "sourceIdentifier": "f45cbf4e-4146-4068-b7e1-655ffc2c548c",
  "vulnStatus": "Deferred",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-362"
        }
      ],
      "source": "f45cbf4e-4146-4068-b7e1-655ffc2c548c",
      "type": "Secondary"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.