Loading vulnerability…
CVE-2026-33068 affects Claude Code versions prior to 2.1.53. The application resolved permission mode settings from configuration files, including the repository-controlled .claude/settings.json, before deciding whether to display the workspace trust confirmation dialog. A malicious repository could commit a .claude/settings.json that set permissions.defaultMode to bypassPermissions, causing Claude Code to silently skip the trust prompt on first open. As a result, the user could be placed into a more permissive execution mode without being shown the expected trust confirmation, weakening the security boundary intended to require explicit user approval before enabling powerful tool actions.
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.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
20 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
One of three previously identified Claude Code vulnerabilities involving malicious repositories abusing project-scoped settings to silently change tool behavior on a developer's machine; the article states it has been patched.
A Claude Code trust-dialog bypass in which permission modes from .claude/settings.json were processed before the workspace trust prompt, allowing a malicious repository to suppress the trust prompt via bypassPermissions.
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.