CVE-2026-47211

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Ouroboros is a local-first runtime for AI coding agents that records their actions and applies user-defined policies to constrain behavior. In versions prior to 0.39.0, if a user clones a malicious repository and runs Ouroboros commands within that directory, it can lead to arbitrary code execution and potential system takeover. The vulnerability stems from Ouroboros loading the .env file from the current working directory. Execution-affecting environment variables such as OUROBOROS_CLI_PATH, OPENCODE_CLI_PATH, and other backend selectors are accepted directly from this local .env. An attacker can include a malicious script in the repository and point the CLI path variable to it (e.g., OUROBOROS_CLI_PATH=./malicious_script.sh). When the user executes a command like ouroboros init or any command that instantiates the adapter, the malicious script is executed instead of the intended CLI. This issue has been fixed in version 0.39.0.

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity84% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

May 29, 2026

Last Modified

August 3, 2026

Advisory Details (3)

Auto-updated Aug 3, 2026
Patch available. Sources: github, github_commit, github_pr.
github Patch Available

Remote Code Execution via Untrusted Project-Directory .env · Advisory · Q00/ouroboros · GitHub

Affected: version 0.39.0 via PR

https://github.com/Q00/ouroboros/security/advisories/GHSA-c4m7-2gwp-vw76
github_pr

fix(security): block RCE via untrusted project-directory .env

Fix merged in Q00/ouroboros PR #1078 on 2026-05-17 — awaiting tagged release

https://github.com/Q00/ouroboros/pull/1078
github_commit

commit 4e70b760b4eb (Q00/ouroboros)

Fix landed in Q00/ouroboros commit 4e70b760b4eb — awaiting tagged release

https://github.com/Q00/ouroboros/commit/4e70b760b4eb157469b58645339ba831f6513d37

Vendor Advisories for CVE-2026-47211(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
ouroboros-ai0.1.0 ... 0.9.0 (302 versions)0.39.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-28 21:41 UTCEPSS rescore
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-25 04:15 UTCEG score recompute
  10. 2026-08-23 14:10 UTCEG score recompute
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-21 23:49 UTCEPSS rescore
  13. 2026-08-20 23:33 UTCEG score recompute
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-20 10:24 UTCEG score recompute
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 06:51 UTCEG score recompute
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 07:42 UTCEG score recompute
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 02:35 UTCEG score recompute
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-14 00:27 UTCEG score recompute
  25. 2026-08-13 22:00 UTCEPSS rescore
Show 28 more
  1. 2026-08-12 15:44 UTCEG score recompute
  2. 2026-08-12 13:51 UTCEPSS rescore
  3. 2026-08-12 02:22 UTCEG score recompute
  4. 2026-08-11 13:19 UTCEG score recompute
  5. 2026-08-11 00:00 UTCEPSS rescore
  6. 2026-08-09 17:53 UTCEG score recompute
  7. 2026-08-09 13:46 UTCEPSS rescore
  8. 2026-08-09 04:51 UTCEG score recompute
  9. 2026-08-08 16:37 UTCEPSS rescore
  10. 2026-08-08 02:01 UTCEG score recompute
  11. 2026-08-06 23:57 UTCEG score recompute
  12. 2026-08-06 13:47 UTCEPSS rescore
  13. 2026-08-05 20:42 UTCEG score recompute
  14. 2026-08-05 19:17 UTCEPSS rescore
  15. 2026-08-04 23:02 UTCEG score recompute
  16. 2026-08-04 15:10 UTCEPSS rescore
  17. 2026-08-03 22:21 UTCEG score recompute
  18. 2026-08-03 21:38 UTCEG score recompute
  19. 2026-08-03 20:21 UTCEG score recompute
  20. 2026-08-03 20:13 UTCEG score recompute▲ 8.40
  21. 2026-08-03 20:13 UTCMITRE cvelistV5CVSS v3 → 8.4 · CVSS v4 → 8.4
  22. 2026-07-31 05:51 UTCEG score recompute
  23. 2026-07-27 03:13 UTCEG score recompute
  24. 2026-07-23 03:17 UTCEG score recompute
  25. 2026-06-14 23:18 UTCEPSS rescore
  26. 2026-06-13 23:00 UTCEPSS rescore
  27. 2026-06-12 23:12 UTCEPSS rescore
  28. 2026-05-29 22:26 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-47211?
CVE-2026-47211 is a high vulnerability published on May 29, 2026. Ouroboros is a local-first runtime for AI coding agents that records their actions and applies user-defined policies to constrain behavior. In versions prior to 0.39.0, if a user clones a malicious repository and runs Ouroboros commands within that directory, it can lead to arbitrary code execution…
When was CVE-2026-47211 disclosed?
CVE-2026-47211 was first published in the National Vulnerability Database on May 29, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47211 actively exploited?
CVE-2026-47211 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.3% of all scored CVEs.
What is the CVSS score of CVE-2026-47211?
CVE-2026-47211 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-47211?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47211, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47211

Explore →

Is Your Infrastructure Affected by CVE-2026-47211?

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

Start Free Scan →Browse All CVEs