# CVE-2025-12740: Remote Command Execution in Looker via IBM DB2 JDBC drive

> A Looker developer can execute arbitrary commands via manipulated LookML and IBM DB2 JDBC parameters, requiring an upgrade for self-hosted instances.

- **Severity:** High 7.7 (`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/U:Red`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Nov 2025
- **Updated:** 24 Nov 2025
- **Also known as:** GHSA-6543-fhjm-g9h2

## What is CVE-2025-12740?

CVE-2025-12740 is a high-severity command injection vulnerability in Google Cloud Looker, published on 24 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Looker user with a Developer role could create a database connection using IBM DB2 driver and, by manipulating LookML, cause Looker to execute a malicious command, due to inadequate filtering of the driver's 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/ :
  *  25.0.93+
  *  25.6.84+

  *  25.12.42+
  *  25.14.50+
  *  25.16.44+

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2025-12740?


## How do I fix CVE-2025-12740?

No fix has been published for CVE-2025-12740 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-12740 being exploited?

There is no known exploitation of CVE-2025-12740 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12740 and fix it if it is affected.

What it is: CVE-2025-12740 is a high-severity command injection vulnerability in Google Cloud Looker, published on 24 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12740 in the wild and no public exploit code.

Affected product: Google Cloud Looker. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-12740/ (Markdown: https://insights.sbomify.com/CVE-2025-12740/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12740
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12740
- OSV: https://osv.dev/vulnerability/CVE-2025-12740

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-12740/
Summaries are generated and may contain mistakes; the official description above is the record.