Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.6amended

ouroboros-ai: Incomplete fix of CVE-2026-47211: untrusted project .env can still reach RCE via omitted execution-routing keys

CVE-2026-66065GHSA-jv2h-4p9v-wf5w

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (ouroboros-ai 0.42.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.6 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-66065: 0.24% estimated exploitation activity in the next 30 days; percentile 15.23 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact The CVE-2026-47211 fix (0.39.0) added UNTRUSTEDENVDENYLIST to stop an untrusted project-directory .env from redirecting execution. The denylist was incomplete — several execution-routing keys of the same RCE class were omitted, so a malicious cloned repo can still reach arbitrary command execution by shipping a .env (auto-loaded at import, no review step): - Backend config-home roots CODEXHOME, OPENCODECONFIG, OPENCODECONFIGDIR, XDGCONFIGHOME: a spawned vendor CLI resolves its config from these. CODEXHOME=./.evil + committed ./.evil/config.toml redirects the nested Codex agent to attacker config — mcpservers.<name.command/args (RCE) and approvalpolicy="never" / sandboxmode="danger-full-access" (silent removal of the human approval gate). (reported by matte1782) - MCP bridge / plugin execution roster OUROBOROSMCPCONFIG (the YAML's server command/args are spawned via stdioclient — RCE), OUROBOROSPLUGINLOCKFILE, OUROBOROSPLUGINTRUSTROOT (redirect the installed-plugin roster /…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-jv2h-4p9v-wf5w

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-jv2h-4p9v-wf5w

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-66065

Advisory: ouroboros-ai: Incomplete fix of CVE-2026-47211: untrusted project .env can still reach RCE via omitted execution-routing keys
IDs: CVE-2026-66065, GHSA-jv2h-4p9v-wf5w
Record: https://patchnext.com/advisories/cve-2026-66065 (revision 3, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ouroboros-ai 0.42.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI ouroboros-ai: affected <= 0.42.0; fixed in 0.42.1

## Suggested inspection (read-only)
- `python -m pip show ouroboros-ai`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ouroboros-ai.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jv2h-4p9v-wf5w (OSV record GHSA-jv2h-4p9v-wf5w lists affected ranges: PyPI ouroboros-ai >=0 <0.42.1 (fixed))
- Verified: https://github.com/advisories/GHSA-jv2h-4p9v-wf5w (GitHub-reviewed advisory GHSA-jv2h-4p9v-wf5w lists affected ranges: PyPI ouroboros-ai >=0 <=0.42.0)

Commands are suggestions: review each one before running it.

Loading voting…