Loading vulnerability…
CVE-2026-64650 affects Vercel's @ai-sdk/harness-codex through version 1.0.28. The relay component used a process-path-based authorization fallback that trusted requests from any process whose command line contained the path of an approved helper script. In Linux environments, untrusted code already executing inside the sandbox could satisfy this check and invoke arbitrary host-exposed tools without a corresponding model-authorized tool-call event. This breaks the intended execution-layer authorization boundary between sandboxed code and host-side tool execution. Exposed operations could include sensitive actions such as secret retrieval, deployment actions, and cloud API operations. Version 1.0.29 removes the process-path authorization fallback and restricts relay acceptance to exact, short-lived, one-time authorizations tied to a bridge-observed model event.
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.