High

Claude Code workspace trust dialog bypass via repo-controlled settings

IdentifiersCVE-2026-33068CWE-285

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.

For your environment

Are you exposed to this one?

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.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker controlling a repository to suppress the workspace trust confirmation and place the victim into a permissive mode without explicit informed consent. This lowers the barrier to subsequent tool execution from the malicious repository and increases the likelihood of unauthorized command or tool actions being performed in the user's environment. The core impact is a bypass of the trust/authorization workflow protecting dangerous operations.

Mitigation

If you can’t patch tonight, do this now.

Until patched, treat repository-provided .claude/settings.json as untrusted input and avoid opening untrusted repositories in Claude Code. Review project-scoped Claude configuration before use, especially any permissions.defaultMode setting. Apply stricter controls on developer workstations and CI environments, and monitor for unexpected tool execution when new repositories are opened.

Remediation

Patch, then assume compromise.

Upgrade Claude Code to version 2.1.53 or later, where this issue is patched. Ensure that workspace trust decisions are made before applying repository-controlled permission settings, and do not allow untrusted project configuration to influence whether trust confirmation is shown.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

AnthropicClaude Codeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

20 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

20 SOURCESView more in app

dark readingNews

May 7, 2026

'TrustFall' Exposes Claude Code Execution Risk

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.

venturebeatNews

Apr 30, 2026

Claude Code, Copilot and Codex all got hacked. Every attacker went for the credential, not the model. | VentureBeat

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.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity18