dbcve.org
Claude DesktopApplication · Anthropic

CVE-2026-44467

MEDIUM · 6.8 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 1.4304.0 or later.
See remediation →
73/100
Remediation priority · Elevated
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
The Claude Desktop app gives you Claude Code with a graphical interface built for running multiple sessions side by side. From 1.2581.0 to before 1.4304.0, Claude Desktop's SSH remote development feature verified only whether a hostname existed in ~/.ssh/known_hosts without comparing the server's presented host key against the stored key. This allowed a network-positioned attacker to present an arbitrary SSH host key and have the connection silently accepted, enabling a man-in-the-middle attack on remote development sessions. Successful exploitation required the attacker to be in a network position to intercept SSH traffic (e.g., via ARP spoofing, rogue Wi-Fi, or DNS poisoning) and the target hostname to already have an entry in the victim's known_hosts file. This vulnerability is fixed in 1.4304.0.

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

The Claude Desktop app's SSH remote development feature from versions 1.2581.0 to before 1.4304.0 had a host key verification bypass. The application checked only whether a hostname existed in ~/.ssh/known_hosts but failed to verify that the server's presented SSH host key matched the stored key, allowing a network-positioned attacker to perform MITM attacks by presenting an arbitrary host key.

MitigationUpgrade Claude Desktop to version 1.4304.0 or later. Additionally, users should remove and re-add host entries in known_hosts to ensure proper key verification is established after the upgrade.

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 DesktopApplication
Affected:>= 1.2581.0, < 1.4304.0

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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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 Desktop version
    Open Claude Desktop, click on the user menu (usually top-right corner), select 'About Claude Desktop' or check the application version in the app settings. Alternatively, on macOS check /Applications/Claude Desktop.app/Contents/Info.plist for CFBundleShortVersionString, or on Windows check the version in Add/Remove Programs.
    Affected if Version is 1.2581.0 or higher but lower than 1.4304.0
  2. Verify SSH remote development is configured
    Check if Claude Desktop has SSH remote development enabled by looking for SSH-related configuration files in the Claude Desktop settings directory. On macOS this is typically ~/Library/Application Support/Claude/, on Windows %APPDATA%\Claude\. Look for any SSH connection configurations or remote development profiles.
    Affected if SSH remote development feature has been configured or used with any remote hosts
  3. Inspect known_hosts for entries
    Examine the file ~/.ssh/known_hosts for entries. If entries exist for any remote development hosts, the application would have checked only for hostname presence without verifying the host key matched, enabling MITM attacks.
    Affected if The ~/.ssh/known_hosts file contains any entries for hosts used with Claude Desktop SSH remote development

A user is affected if they have Claude Desktop installed with version 1.2581.0 or higher but lower than 1.4304.0 and have used the SSH remote development feature with hosts listed in ~/.ssh/known_hosts.

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.4304.0 or later
Fixed in 1.4304.0
Interim mitigation

Upgrade Claude Desktop to version 1.4304.0 or later. Additionally, users should remove and re-add host entries in known_hosts to ensure proper key verification is established after the upgrade.

Recommended fix High confidence

1.4304.0

  1. Check current Claude Desktop version via the app's About or Help menu
  2. Download Claude Desktop version 1.4304.0 or later from the official Anthropic website or GitHub releases
  3. Install the update by running the downloaded installer
  4. Verify the new version is running after installation

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

Fix this in Claude Desktop Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44467 — 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-2026-44467 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