CVE-2026-47211

HighCVSS 8.4

Published: 03/08/2026(UTC)Updated: 03/08/2026(UTC)Translated: 04/08/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.17%

7th percentile - higher than 7% of all known CVEs

Summary

Ouroboros before version 0.39.0 loads the .env file from the current working directory, allowing injection of malicious environment variables. Cloning a malicious repository and running Ouroboros commands can lead to arbitrary code execution and system takeover.

Risk Assessment

An attacker can take over the AI developer's system by executing malicious code in the victim's context. This can lead to data theft, backdoor installation, or full workstation compromise.

Recommendation

Immediately update Ouroboros to version 0.39.0 or later. Avoid cloning and running the tool in untrusted repositories.

Other vulnerabilities in Ouroboros

CVE-2026-66065High
Ouroboros, a runtime for AI coding agents, prior to version 0.42.1, has an incomplete denylist. Despite a previous fix (CVE-2026-47211), some keys enabling remote code execution (RCE) were not blocked. A malicious repository can use a .env file to bypass security and execute arbitrary commands. Fixed in version 0.42.1.

Original NVD description (English source)

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.