# CVE-2026-132122: agentic-radar 0.7.0 before 0.14.2 OpenAI API Key Leak via Untrusted .env Loading


- **Severity:** Medium 5.7 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-wjf7-gf9m-35rq

## What is CVE-2026-132122?

CVE-2026-132122 is a medium-severity vulnerability in splx-ai agentic-radar, published on 18 Nov 2026. 

### Official description

agentic-radar 0.7.0 before 0.14.2 contains an untrusted configuration loading vulnerability that allows malicious repositories to inject environment variables by having load_dotenv() in agentic_radar/cli.py load the scanned repository's .env file. Attackers can set OPENAI_BASE_URL to an attacker-controlled host so that scan openai-agents or --harden-prompts send requests carrying the user's OpenAI API key to the attacker.

Weakness: CWE-15 (External Control of System or Configuration Setting)

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

1 open source package ship an affected version, including agentic-radar.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `agentic-radar` | PyPI | `pkg:pypi/agentic-radar` | From 0.7.0 | 0.14.2 |

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

Upgrade agentic-radar to 0.14.2 or later.

## Is CVE-2026-132122 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-132122 is a medium-severity vulnerability in splx-ai agentic-radar, published on 18 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-132122 exists.

Affected packages and fixed versions:
- agentic-radar (PyPI): affected from 0.7.0; fixed in 0.14.2

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-132122/ (Markdown: https://insights.sbomify.com/CVE-2026-132122/index.md)
```

## Sources

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

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