The vulnerability exists in deepseek-harness versions up to 0.1.5‑rc.3. An argument known as E2B_API_KEY is passed to an internal function within packages/e2b/e2b/src/index.ts without proper validation and is subsequently used to make a security decision. Because the argument originates from untrusted input, a local user who can influence the key can alter the logic that determines access or privileges. The lack of input validation maps to CWE‑20, and the misuse in a security decision aligns with CWE‑807. The immediate consequence is that a local attacker could potentially elevate privileges or execute unintended operations within the harness environment, jeopardizing system integrity.

The affected product is deepseek‑AI’s deepseek‑harness component. Versions up to 0.1.5‑rc.3 are vulnerable. No specific operating system or platform information is provided; the vulnerability is tied to the application code within the harness regardless of the host environment.

The CVSS score of 4.8 places the issue in the moderate range. EPSS is not available, so the exploitation probability cannot be quantified, but the description states that the exploit is publicly available and may be used, indicating that local users have the ability to perform the attack. The vulnerability requires local access, meaning the threat surface is limited to users or processes that can interact with the harness directly. As it is not currently listed in CISA KEV, there is no formal indication of known exploitation in the wild, but the public availability of an exploit suggests a realistic risk for systems that allow local manipulation of the E2B_API_KEY value.