dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-12155

HIGH · 7.1 CVSS v4.0 Published 2025-11-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable

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 · unedited
A Command Injection vulnerability, resulting from improper file path sanitization (Directory Traversal) in Looker allows an attacker with Developer permission to execute arbitrary shell commands when a user is deleted on the host system. 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.100+ * 24.18.192+ * 25.0.69+ * 25.6.57+ * 25.8.39+ * 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 confidence

A Command Injection vulnerability exists in Looker due to improper file path sanitization (Directory Traversal). An attacker with Developer permission can execute arbitrary shell commands when a user is deleted on the host system.

MitigationSelf-hosted instances must be upgraded to one of the patched versions (24.12.100+, 24.18.192+, 25.0.69+, 25.6.57+, 25.8.39+, or 25.10.22+) as soon as possible. Looker-hosted instances require no action as they are already mitigated.

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
Low
Privileges
High
Authentication
Y
User interaction
A
Scope
P

CVSS:4.0/AV:N/AC:L/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:P/AU:Y/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine if Looker is self-hosted
    Check if the Looker instance is self-hosted (on-premises) or Looker-hosted (SaaS). Looker-hosted instances are already mitigated. Inspect your deployment documentation or contact your Looker administrator to confirm the hosting type.
    Affected if The instance is self-hosted (on-premises)
  2. Identify the installed Looker version
    Access the Looker admin panel and navigate to About or Settings, or run the command: looker --version (if CLI is available). Alternatively, check the installation directory for a version file or the Looker startup logs.
    Affected if The installed version is earlier than 24.12.100, 24.18.192, 25.0.69, 25.6.57, 25.8.39, or 25.10.22 (or if version cannot be determined)
  3. Verify Developer role permissions exist
    In the Looker admin panel, navigate to Users and Roles, or query the Looker database for users with Developer permissions. Check if any users are assigned the Developer role.
    Affected if Users with Developer role permissions exist in the system
  4. Confirm user deletion functionality is accessible
    In the Looker admin panel, navigate to Users section and verify if the option to delete users is available. Ensure that users with Developer permissions can access the deletion functionality or that admin users can perform deletions.
    Affected if User deletion functionality is enabled and accessible

A self-hosted Looker instance running an unpatched version (before the listed patch releases) with Developer role permissions and user deletion functionality enabled is likely affected by this vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Self-hosted instances must be upgraded to one of the patched versions (24.12.100+, 24.18.192+, 25.0.69+, 25.6.57+, 25.8.39+, or 25.10.22+) as soon as possible. Looker-hosted instances require no action as they are already mitigated.

Recommended fix High confidence

24.12.100+ or 24.18.192+ or 25.0.69+ or 25.6.57+ or 25.8.39+ or 25.10.22+

  1. 1. Identify the current version of your self-hosted Looker instance by checking the Looker administration panel or running the Looker version command.
  2. 2. Determine which upgrade path applies based on your current version (24.12.x, 24.18.x, 25.0.x, 25.6.x, 25.8.x, or 25.10.x).
  3. 3. Navigate to the Looker download page at https://download.looker.com/ and download the appropriate fixed version for your upgrade path.
  4. 4. Review the Looker upgrade documentation and release notes for your target version to ensure compatibility with your environment.
  5. 5. Backup your Looker instance data and configuration files before proceeding with the upgrade.
  6. 6. Perform the upgrade following Looker's standard upgrade procedure for self-hosted instances.
  7. 7. After upgrade completion, verify the Looker service is running correctly and confirm the version has been updated to the patched release.
  8. 8. Test that Looker functionality works normally, particularly user management and developer features.
Caveat Review Looker release notes for your target version to check for any breaking changes or required migration steps before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12155 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12155 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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