dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-12741

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

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 Looker user with Developer role could create a database connection using Denodo driver and, by manipulating LookML, cause Looker to execute a malicious command. 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.108+ * 24.18.200+ * 25.0.78+ * 25.6.65+ * 25.8.47+ * 25.12.10+ * 25.14+

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

Authenticated Developer role users could create a database connection using the Denodo driver and manipulate LookML to cause Looker to execute arbitrary commands. This is a command injection vulnerability via the Denodo driver and LookML configuration.

MitigationLooker-hosted instances are already protected. Self-hosted customers must upgrade to version 24.12.108+, 24.18.200+, 25.0.78+, 25.6.65+, 25.8.47+, 25.12.10+, or 25.14+ as soon as possible.

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
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/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 checks

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

  1. Identify Looker version
    Check the installed Looker version in the admin panel under Looker or using the version endpoint. Compare against the fixed versions: 24.12.108+, 24.18.200+, 25.0.78+, 25.6.65+, 25.8.47+, 25.12.10+, 25.14+.
    Affected if The installed version is lower than any of these fixed versions.
  2. Review database connections for Denodo driver
    Navigate to the Admin panel in Looker and examine all database connections. Look for connections that use the Denodo driver.
    Affected if Any database connection is configured to use the Denodo driver.
  3. Audit Developer role assignments
    In the Looker Admin panel under Users, review which users are assigned the Developer role.
    Affected if There are one or more users with Developer role access.
  4. Examine LookML configurations for Denodo-based connections
    Review all LookML files and models that reference Denodo database connections. Check the explores and views associated with these connections.
    Affected if Any LookML is using a Denodo-based database connection.

A user is affected if they are running a Looker version below the fixed versions AND have Denodo driver connections in use with Developer role users who can modify LookML.

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

Looker-hosted instances are already protected. Self-hosted customers must upgrade to version 24.12.108+, 24.18.200+, 25.0.78+, 25.6.65+, 25.8.47+, 25.12.10+, or 25.14+ as soon as possible.

Recommended fix High confidence

Upgrade to Looker version 25.14 or later, or to one of the specific patched versions (24.12.108+, 24.18.200+, 25.0.78+, 25.6.65+, 25.8.47+, 25.12.10+)

  1. 1. Identify your current Looker Self-hosted version by checking the Looker administration panel or running the Looker version command
  2. 2. Determine which upgrade path applies to your current version based on the supported fixed versions: 24.12.108+, 24.18.200+, 25.0.78+, 25.6.65+, 25.8.47+, 25.12.10+, or 25.14+
  3. 3. Download the appropriate fixed version from the Looker download page at https://download.looker.com/
  4. 4. Review the Looker upgrade documentation for your deployment type (traditional or containerized)
  5. 5. Perform a backup of your Looker instance configuration and data
  6. 6. Schedule a maintenance window as upgrades require downtime
  7. 7. Execute the upgrade following the documented upgrade procedure
  8. 8. Verify the upgrade was successful by checking the Looker version in the administration panel

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12741 — 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-12741 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