Loading vulnerability…
CVE-2026-64651 is an authorization flaw in @ai-sdk/harness-opencode affecting versions through 1.0.27. The package connects HarnessAgent to OpenCode through a sandboxed bridge, but the vulnerable relay accepted requests from any process whose command line contained the path of an approved helper script. In the Linux-specific fallback path, the relay inspected process information via /proc and treated the presence of the helper script path in the command line as sufficient authorization. As a result, untrusted code already executing inside the sandbox could satisfy the check and invoke arbitrary host-exposed tools without a corresponding model-authorized tool-call event. This is an execution-layer authorization bypass that breaks the intended trust boundary between sandboxed code and host tool execution.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.