CVE-2025-12472
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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+
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA race condition vulnerability exists in Looker's LookML project handling during Git directory deletion. An attacker with Developer role privileges can manipulate a LookML project to trigger the race condition, leading to arbitrary command execution on the Looker instance. The vulnerability affects self-hosted deployments and has been patched in the specified version updates.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- High
- Authentication
- X
- User interaction
- A
- Scope
- X
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
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Looker deployment typeIdentify whether the Looker instance is self-hosted (on-premises or customer-managed cloud) or Looker-hosted (Google Cloud-hosted). Check deployment documentation or contact the infrastructure team.Affected if The instance is self-hosted; Looker-hosted instances are already mitigated.
-
Determine installed Looker versionAccess the Looker admin panel, navigate to About or Version information, or use the Looker API endpoint /api/3.0/about to retrieve the version number.Affected if The installed version is earlier than 24.12.103, 24.18.195, 25.0.72, 25.6.60, 25.8.42, or 25.10.22 (or does not appear in the patched release list).
-
Review user role assignmentsIn Looker admin settings, navigate to Users and Roles. Identify accounts assigned the Developer role, which grants LookML project write access.Affected if One or more users hold Developer role privileges, providing the baseline access needed to trigger the race condition.
-
Audit recent LookML project changesReview Git history or Looker project audit logs for any unusual or unauthorized LookML project modifications, particularly involving Git directory operations or rapid sequential changes.Affected if Suspicious or unauthorized LookML project manipulations involving Git directories are present in recent activity logs.
-
Inspect for abnormal command executionReview Looker server logs (looker.log, startup logs) and any integrated monitoring for unexpected command invocations or script executions originating from LookML project processing.Affected if Unexpected commands or script executions appear in logs that cannot be traced to legitimate administrative actions.
A self-hosted Looker instance running an unpatched version with Developer role users present is likely affected if the environment shows signs of LookML project manipulation or unexplained command execution.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedSelf-hosted instances must be upgraded to one of the patched versions (24.12.103+, 24.18.195+, 25.0.72+, 25.6.60+, 25.8.42+, or 25.10.22+) as soon as possible. Looker-hosted instances require no action as they are already mitigated.
Upgrade to any of: 24.12.103+, 24.18.195+, 25.0.72+, 25.6.60+, 25.8.42+, or 25.10.22+ (preferably the latest in your release branch)
- 1. Identify the current self-hosted Looker version by checking the Looker administration panel or running 'looker --version'
- 2. Determine which upgrade path applies based on current version - users should upgrade to at least one of: 24.12.103+, 24.18.195+, 25.0.72+, 25.6.60+, 25.8.42+, or 25.10.22+
- 3. Access the Looker download page at https://download.looker.com/ to obtain the appropriate patched version
- 4. Follow Looker's standard upgrade documentation to apply the update
- 5. After upgrade, verify the new version is running and confirm the vulnerability is patched
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12472 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12472 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data