CVE-2026-132122

MEDIUMPre-NVD 4.74.7
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 4.7 from GitHub Security Advisory (severity: MODERATE) published 2026-11-18. A secondary CVSS source baseline 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-128623 (ENISA EUVD) · GHSA-wjf7-gf9m-35rq (GitHub Security Advisories)Source: ENISA EUVD

4.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
4.7
EG Score
4.7MEDIUMhigh confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity47% × 45%
Impact severity (EG Severity): CVSS 4.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.7): severity, escalated by confirmed exploitation. This CVE's 4.7 is its impact severity (EG Severity), not escalated.

EG Severity
4.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 18, 2026

Last Modified

November 18, 2026

Advisory Details (6)

Auto-updated Nov 18, 2026
Patch available. Sources: github_commit, github_pr, github_release.
Web page

agentic-radar 0.7.0 before 0.14.2 OpenAI API Key Leak via Untrusted .env Loading | Advisories | VulnCheck

https://www.vulncheck.com/advisories/agentic-radar-0.7.0-before-0.14.2-openai-api-key-leak-via-untrusted-env-loading
Web page

GitHub - Teycir/agentic-radar-cve: Private pre-disclosure pack: agentic-radar (PyPI) API key exfiltration via repository-controlled .env — GitHub CNA submission · GitHub

https://github.com/Teycir/agentic-radar-cve
Web page

GitHub - splx-ai/agentic-radar: A security scanner for your LLM agentic workflows · GitHub

https://github.com/splx-ai/agentic-radar
GitHub release Patch Available

v0.14.2

Patch available: splx-ai/agentic-radar v0.14.2

https://github.com/splx-ai/agentic-radar/releases/tag/v0.14.2
GitHub commit Patch Available

commit b99bb14fc1d9 (splx-ai/agentic-radar)

Patch available: splx-ai/agentic-radar v0.14.2 (contains commit b99bb14fc1d9)

https://github.com/splx-ai/agentic-radar/commit/b99bb14fc1d9c4bab0bf2752d4547f79077960fe
GitHub pull request Patch Available

fix: load .env only from an explicit --env-file path

Patch available: splx-ai/agentic-radar v0.14.2 (PR #134 merged 2026-11-13)

https://github.com/splx-ai/agentic-radar/pull/134

Vendor Advisories for CVE-2026-132122(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-11-19 22:58 UTCEchelonGraph re-scored
  4. 2026-11-19 22:58 UTCGHSA enrichmentGHSA-wjf7-gf9m-35rq · GitHub severity MODERATE · GitHub CVSS 4.7
  5. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-11-18 18:30 UTCGHSA enrichmentGHSA-wjf7-gf9m-35rq · GitHub severity MODERATE · GitHub CVSS 4.7
  7. 2026-11-18 15:47 UTCEchelonGraph re-scored
  8. 2026-11-18 15:47 UTCGHSA enrichmentGHSA-wjf7-gf9m-35rq · GitHub severity MODERATE · GitHub CVSS 4.7
  9. 2026-11-18 13:28 UTCEchelonGraph re-scored
  10. 2026-11-18 13:03 UTCENISA EUVD ID recordedEUVD-2026-128623 · Source: ENISA EUVD
  11. 2026-11-18 12:23 UTCEchelonGraph re-scoredFirst assessed: 4.7 MEDIUM
  12. 2026-11-18 12:22 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-132122?
CVE-2026-132122 is a medium-severity vulnerability; its CVE record was published on November 18, 2026. 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…
When was CVE-2026-132122 made public?
CVE-2026-132122 was made public on November 13, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 18, 2026. EchelonGraph's copy of the record carries a last-modified date of November 18, 2026; the record at its source may have been updated since.
Is CVE-2026-132122 actively exploited?
CVE-2026-132122 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-132122?
CVE-2026-132122 has a CVSS base score of 4.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-132122?
A fix for CVE-2026-132122 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-132122 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-132122

Explore →

Is Your Infrastructure Affected by CVE-2026-132122?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.