CVE
Agentic Radar API key leak via untrusted .env loading in CLI
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 0.14.2
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.14.2.
Summary
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.
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure?/25Unknown. No advisory context yet
- Reach10/20Affects PyPI packages
- Severity5.7/10CVSS 5.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 53 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.14.2.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132122 (agentic-radar 0.7.0 before 0.14.2 OpenAI API Key Leak via Untrusted .env Loading), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132122 (entry last updated 2026-11-18):
Affected:
- PyPI package agentic-radar: from 0.7.0, fixed in 0.14.2
Fixed versions: 0.14.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132122 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132122 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (PyPI): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/splx-ai/agentic-radar/pull/134
- https://github.com/splx-ai/agentic-radar/commit/b99bb14fc1d9c4bab0bf2752d4547f79077960fe
- https://github.com/splx-ai/agentic-radar/releases/tag/v0.14.2
- https://github.com/splx-ai/agentic-radar
- https://www.vulncheck.com/advisories/agentic-radar-0.7.0-before-0.14.2-openai-api-key-leak-via-untrusted-env-loading
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132122
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132122"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- agentic-radarPyPI
From 0.7.0 · fixed in 0.14.2
Evidence 8
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132122 |
| Record | NVD · CVE-2026-132122 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · Teycir/agentic-radar-cve · Repository |
| Other links 5 | |
| Patch | GitHub · splx-ai/agentic-radar · Pull request #134 |
| Patch | GitHub · splx-ai/agentic-radar · Commit b99bb14f |
| Repository | GitHub · splx-ai/agentic-radar · Release v0.14.2 |
| Repository | GitHub · splx-ai/agentic-radar · Repository |
| Link | vulncheck.com · advisories/agentic-radar-0.7.0-before-0.14.2-openai-api-key-leak-via-untrusted-env-loading |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-132122
Is CVE-2026-132122 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-132122?
agentic-radar (PyPI): from 0.7.0 before 0.14.2.Source: cve.now feed data
How do I fix CVE-2026-132122?
Upgrade to a fixed version: 0.14.2.Source: cve.now feed data