# CVE-2026-75062: Eval Injection in google/langfun via default lf.query protocol

> Remote attackers can execute arbitrary Python code via crafted prompts in the default query protocol of the Google langfun library.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Aug 2026
- **Updated:** 27 Aug 2026
- **Also known as:** GHSA-8x83-862f-c85r

## What is CVE-2026-75062?

CVE-2026-75062 is a critical code injection vulnerability in Google langfun, published on 26 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') in the default lf.query Python protocol in Google langfun versions prior to 0.1.2 allows remote unauthenticated attackers to execute arbitrary Python code in the context of the host application via crafted prompt inputs that cause the model to generate executable Python expressions evaluated without a sandbox.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code), CWE-1188 (Initialization of a Resource with an Insecure Default)

## Which versions are affected by CVE-2026-75062?


## How do I fix CVE-2026-75062?

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

## Is CVE-2026-75062 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75062 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75062 and fix it if it is affected.

What it is: CVE-2026-75062 is a critical code injection vulnerability in Google langfun, published on 26 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75062 exists.

Affected product: Google langfun. 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-2026-75062/ (Markdown: https://insights.sbomify.com/CVE-2026-75062/index.md)
```

## Sources

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

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