CVE-2026-47211
Local .env parsing allows arbitrary code execution when running Ouroboros in a cloned malicious repo.
Is CVE-2026-47211 being exploited?
Not confirmed. CVE-2026-47211 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.17% probability of exploitation in the next 30 days.
How severe is CVE-2026-47211?
CVE-2026-47211 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-47211?
Yes. A fix has been recorded for CVE-2026-47211. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-47211 affect?
CVE-2026-47211 affects Ouroboros < 0.39.0 (local-first AI coding runtime). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-47211?
Upgrade to Ouroboros v0.39.0 and avoid running it in untrusted repositories.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker-controlled .env can set CLI paths (e.g., OUROBOROS_CLI_PATH) to execute arbitrary scripts, enabling local code execution and potential system takeover.
Immediate action required
- affected< 0.39.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.