dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-12742

HIGH · 7.5 CVSS v4.0 Published 2025-11-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/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 a Developer role could cause Looker to execute a malicious command, due to insecure processing of Teradata driver parameters. 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

This is a command injection vulnerability in Looker's Teradata database driver. A user with Developer role can inject malicious commands through insecure processing of Teradata driver parameters, allowing arbitrary command execution on the Looker server.

MitigationSelf-hosted Looker instances must be upgraded immediately to a patched version (24.12.108+, 24.18.200+, 25.0.78+, 25.6.65+, 25.8.47+, 25.12.10+, or 25.14+). Looker-hosted instances require no action as they are already patched.

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
None
Scope
X

CVSS:4.0/AV:N/AC:H/AT:P/PR:H/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
    Navigate to Admin > Looker or use the /api/info endpoint to determine the installed Looker version number
    Affected if The version is earlier than 24.12.108, 24.18.200, 25.0.78, 25.6.65, 25.8.47, 25.12.10, or 25.14
  2. Check for Teradata database connections
    Navigate to Admin > Database > Connections to list all configured database connections. Look for any connection using the Teradata driver
    Affected if A Teradata connection is configured and enabled in Looker
  3. Identify users with Developer role
    Navigate to Admin > Users and filter or check the role assignment for each user. Alternatively, use the API endpoint /api/users to list users and their roles
    Affected if There are users assigned the Developer role in Looker
  4. Verify Developer role access to Teradata
    In Admin > Database > Connections, select the Teradata connection and review which roles are permitted to access it. Check if Developer role is granted access
    Affected if Users with Developer role have permission to access a Teradata connection

You are affected if your Looker version is unpatched AND you have an active Teradata connection accessible to users with Developer role, as this combination allows the command injection to be exploited.

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 Looker instances must be upgraded immediately to a patched version (24.12.108+, 24.18.200+, 25.0.78+, 25.6.65+, 25.8.47+, 25.12.10+, or 25.14+). Looker-hosted instances require no action as they are already patched.

Recommended fix High confidence

24.12.108+ or 24.18.200+ or 25.0.78+ or 25.6.65+ or 25.8.47+ or 25.12.10+ or 25.14+ (choose the appropriate version for your upgrade path)

  1. 1. Identify your current Looker Self-hosted version by checking the Looker administration panel or running `looker --version`.
  2. 2. Determine which upgrade path applies based on your current version - choose the next supported version from the fixed releases list.
  3. 3. Download the appropriate fixed version from https://download.looker.com/ as specified in the advisory.
  4. 4. Follow Looker's standard upgrade procedure for Self-hosted instances, ensuring you have a backup of your configuration and data.
  5. 5. After upgrading, verify the Looker instance is operational and the Teradata connection functionality works correctly.
Caveat Review Looker release notes for breaking changes between your current version and the target version 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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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