SEPTEMBER 7, 2026
Live Feed
Back to database
Case File

CVE-2026-64650

MEDIUM · CVSS 6.3 EPSS 0.11% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-07-20 · Last synced 2026-08-19

CyberRota Analysis

AI-Generated

The `@ai-sdk/harness-opencode` tool in versions prior to 1.0.29 is vulnerable on Linux systems, allowing untrusted code in a sandbox to invoke arbitrary host-exposed tools, potentially leading to unauthorized access to sensitive operations like secret lookups and cloud API calls. This vulnerability requires an active harness session and can be exploited by malicious dependencies or scripts. Organizations using this tool, especially in environments where untrusted code may be executed, should prioritize upgrading to version 1.0.29 or implementing workarounds to mitigate the risk.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Detected Signals
exploit

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-64650
Severity
MEDIUM
CVSS
6.3
EPSS
0.11%
Linux

Original NVD Description

The `@ai-sdk/harness-opencode` tool is an HarnessV1 adapter backed by @openai/codex-sdk, which drives the codex command line interface. Prior to version 1.0.29, the tool relay authorizes requests from any process whose command line contains an allowed helper script path (the Codex CLI shim). This allows untrusted code executing in the sandbox to invoke arbitrary host-exposed tools, including secret lookups, deployment operations, and cloud API calls without a corresponding model-authorized tool-call event. Exploitation requires a Linux environment (the vulnerable fallback checks `process.platform === 'linux'` and reads `/proc`); an active harness session with one or more host-provided tools; and untrusted code executing in the sandbox (e.g. a malicious dependency, build script, or lifecycle hook) The fix in version 1.0.29 removes the process-path authorization fallback entirely. Relay requests are now only accepted after exact, short-lived, one-time authorization matching the tool name and input from a bridge-observed model event. Some workarounds are available. Do not run the Codex harness on untrusted repositories or with untrusted dependencies, and/or limit host-exposed tools to non-sensitive operations when working with untrusted code.