The vulnerability originates from an incomplete denylist in the Ouroboros runtime that allows certain execution‑routing keys to bypass the approval gate. As a result, a malicious .env file placed in a cloned repository can trigger arbitrary command execution when the runtime automatically loads it, without any review step. The weakness aligns with CWE‑15 (External Control of System or Process Parameters) and CWE‑94 (Improper Control of Generation of Code Through a Function That Accepts Input), implying both uncontrolled environment variables and code generation misuse.

Vendor Q00 provides the Ouroboros local‑first runtime. Versions older than 0.42.1 are vulnerable, as the fix that fully expands the denylist was introduced in release 0.42.1.

The CVSS score of 8.4 indicates high severity, although no EPSS score is available and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is that an adversary provides a repository containing a crafted .env file; upon import, the runtime loads it and the attacker gains arbitrary local command execution. Since the runtime operates in a local‑first context, this could lead to complete compromise of the host environment or any services running the runtime. The incomplete denylist means many execution‑routing keys remain exploitable, increasing the likelihood that a successful exploit can be achieved in a real deployment.