dbcve.org
Claude CodeApplication · Anthropic

CVE-2025-59041

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-10
Fix available
A fix is available. Upgrade to 1.0.105 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Claude Code is an agentic coding tool. At startup, Claude Code executed a command templated in with `git config user.email`. Prior to version 1.0.105, a maliciously configured user email in git could be used to trigger arbitrary code execution before a user accepted the workspace trust dialog. Users on standard Claude Code auto-update will have received this fix automatically. Users performing manual updates are advised to update to version 1.0.105 or the latest version.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Claude Code versions before 1.0.105 executed a command at startup that incorporated the `git config user.email` value without proper sanitization. An attacker with write access to a user's git configuration could set a malicious user email containing shell metacharacters to achieve arbitrary code execution before the workspace trust dialog appeared.

MitigationUpdate Claude Code to version 1.0.105 or later. Verify that auto-update is enabled, or manually apply the latest version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Claude CodeApplication
Affected:< 1.0.105

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Claude Code version
    Run 'claude --version' or check the application's version information in its UI or about dialog. Compare the version number to 1.0.105.
    Affected if The installed version is less than 1.0.105.
  2. Inspect git config user.email for shell metacharacters
    Run 'git config --global user.email' to retrieve the configured email address. Manually inspect the value for special shell characters such as semicolons (;), pipes (|), ampersands (&), dollar signs ($), backticks (`), parentheses (), or quotes.
    Affected if The user.email value contains any shell metacharacters that could be interpreted as command separators or injection points.
  3. Check for local repository git configuration
    If checking a specific project directory, run 'git config user.email' within that repository to check the local git config, in addition to the global check.
    Affected if The local repository user.email contains shell metacharacters.
  4. Verify workspace trust dialog behavior
    Observe whether Claude Code displays a workspace trust dialog upon startup. This check confirms the application is reaching the vulnerable startup phase.
    Affected if The workspace trust dialog appears (indicates the application is executing the vulnerable startup command).

You are affected if Claude Code version is below 1.0.105 AND the git config user.email contains shell metacharacters that could be executed during startup.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.105 or later
Fixed in 1.0.105
Interim mitigation

Update Claude Code to version 1.0.105 or later. Verify that auto-update is enabled, or manually apply the latest version.

Recommended fix High confidence

1.0.105 or latest

  1. Download Claude Code version 1.0.105 or the latest version from the official Anthropic website or GitHub releases
  2. Install or update Claude Code to version 1.0.105 or the latest available version
  3. Verify the installed version is 1.0.105 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Claude Code Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59041 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59041 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data