Skip to main content

PuTTY CVE-2026-48850

| EUVDEUVD-2026-31729 MEDIUM
Double Free (CWE-415)
2026-05-25 mitre GHSA-c27j-mcjp-93gg
5.9
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Attacker operates malicious SSH server
  2. Delivery
    Victim initiates PuTTY SSH connection
  3. Exploit
    Server negotiates RSA key exchange
  4. Execution
    Crafted RSA KEX response triggers double free
  5. Persist
    PuTTY heap corruption
  6. Impact
    Client process crashes (DoS)

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Double free prevention
Exploitation Conditions

The vulnerability requires that RSA key exchange be negotiated during the SSH handshake - meaning either the server offers RSA KEX and PuTTY accepts it, or PuTTY's KEX algorithm preference list includes RSA methods (which is common in default PuTTY configurations). CVSS PR:N confirms no authentication is required from the attacker's perspective: the attacker operates as the server (or MITM), not as an authenticated SSH client. CVSS AC:H is the primary limiting factor, indicating that triggering the double free reliably requires conditions beyond a simple connect-and-send, such as specific heap state or protocol sequencing. CVSS UI:N means no victim interaction beyond initiating the SSH connection is needed. The scope is limited to the PuTTY client process itself (S:U), so exploitation cannot directly pivot to other processes or users on the system. Exploitation is further limited to PuTTY versions 0.72-0.83 specifically; other SSH clients are not affected by this CVE.

Impact

Multiple signals converge on a low real-world risk assessment. The CVSS 3.7 Low score reflects high attack complexity (AC:H), no confidentiality or integrity impact (C:N/I:N), and only limited availability impact (A:L). EPSS at 0.04% (12th percentile) is very low, indicating the broader security community does not expect widespread exploitation in the near term. SSVC analysis confirms exploitation status as none, the attack is not automatable, and technical impact is partial - all pointing away from prioritized emergency response. There is no CISA KEV listing and no public exploit code identified at time of analysis. One notable data inconsistency: the tag 'Information Disclosure' conflicts with the CVSS C:N (no confidentiality impact) rating; this discrepancy is not resolved in the available data and may reflect a tagging error or a secondary, unscored behavior described in the vendor wishlist page. Defenders should not treat this as a high-priority emergency but should schedule remediation as part of normal patch cycles for internet-facing or sensitive SSH client deployments.

Exploit ScenarioDerived

A user running vulnerable PuTTY (0.72-0.83) connects to an attacker-controlled or compromised SSH server. The server negotiates RSA key exchange, and upon processing the crafted RSA KEX response, PuTTY triggers the double free condition, causing a crash or potential heap corruption. The AC:H CVSS rating indicates this requires specific conditions - likely precise heap layout or server-side sequencing - making reliable exploitation difficult but not impossible in targeted scenarios.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 08, 2026

Double free in PuTTY's RSA key exchange implementation affects versions 0.72 through 0.83, creating a memory corruption condition that can crash the client when connecting to a server that negotiates RSA KEX. The CVSS vector (AV:N/AC:H/PR:N/UI:N/A:L) reflects a network-reachable but high-complexity trigger with only limited availability impact, consistent with a difficult-to-reproduce crash rather than reliable code execution. No active exploitation is confirmed per CISA KEV, SSVC reports exploitation status as none, and EPSS sits at 0.04% (12th percentile), indicating low real-world exploitation pressure at time of analysis.

RemediationAI

Upgrade to PuTTY 0.84 or later, the vendor-released patch confirmed via the official PuTTY announcement mailing list (https://lists.tartarus.org/pipermail/putty-announce/2026/000042.html). The upstream maintainer's wishlist entry (https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/rsakex-double-free.html) provides additional context on the fix. If immediate upgrade is not possible, a specific compensating control is to configure PuTTY's SSH key exchange algorithm list to exclude RSA KEX methods (e.g., rsa2048-sha256, rsa1024-sha1) and enforce only non-RSA key exchange algorithms such as ECDH or curve25519-sha256 in PuTTY's connection settings under SSH > Kex. This prevents the vulnerable code path from being exercised entirely, though it may cause compatibility issues with older SSH servers that support only RSA KEX. Enterprise deployments using centrally managed PuTTY configurations (e.g., via Pageant or Plink in scripts) should apply the upgrade promptly to avoid unmanaged exposure.

Affected VersionsENISA

PuTTY 0.72 <0.84

Affected Packages

euvd putty fix: 0.84

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

PuTTY is a widely used open-source SSH and Telnet client (CPE: cpe:2.3:a:putty:putty:*:*:*:*:*:*:*:*). The vulnerability is rooted in CWE-415 (Double Free), a memory-safety flaw where a heap-allocated buffer is freed more than once during RSA key exchange (RSA KEX) - the phase of the SSH handshake where asymmetric cryptography is used to negotiate session keys. In PuTTY's RSA KEX code path, a code path error causes the same memory region to be released twice, corrupting the heap allocator's internal state. While double-free conditions can theoretically be escalated to arbitrary code execution via heap feng shui techniques, the AC:H rating and low CVSS score suggest the practical exploitability is constrained by timing, heap layout, or other environmental factors. The vulnerability is present across versions 0.72 up to (but not including) 0.84, per both EUVD-2026-31729 and the upstream vendor advisory.

Know when Putty gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.9 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
SUSE MEDIUM

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

3
Severity Changed
Jul 24, 2026 - 10:22 NVD
LOW MEDIUM
CVSS changed
Jul 24, 2026 - 10:22 NVD
3.7 (LOW) 5.9 (MEDIUM)
Patch available
May 26, 2026 - 14:01 EUVD

DescriptionNVD

PuTTY 0.72 before 0.84 has a double free in RSA KEX.

Threat Intelligence Overview

EPSS Score
0.0%
Top 88% exploitable
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment Vendor VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

More in Putty

View all
CVE-2023-48795 MEDIUM POC
5.9 Dec 18

The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remot

CVE-2016-2563 CRITICAL POC
9.8 Apr 07

Stack-based buffer overflow in the SCP command-line utility in PuTTY before 0.67 and KiTTY 0.66.6.3 and earlier allows r

CVE-2017-6542 CRITICAL POC
9.8 Mar 27

The ssh_agent_channel_data function in PuTTY before 0.68 allows remote attackers to have unspecified impact via a large

CVE-2016-6167 HIGH POC
7.8 Jan 30

Multiple untrusted search path vulnerabilities in Putty beta 0.67 allow local users to execute arbitrary code and conduc

CVE-2021-33500 HIGH POC
7.5 May 21

PuTTY before 0.75 on Windows allows remote servers to cause a denial of service (Windows GUI hang) by telling the PuTTY

CVE-2019-17067 CRITICAL
9.8 Oct 01

PuTTY before 0.73 on Windows improperly opens port-forwarding listening sockets, which allows attackers to listen on the

CVE-2019-9898 CRITICAL
9.8 Mar 21

Potential recycling of random numbers used in cryptography exists within PuTTY before 0.71. Rated critical severity (CVS

CVE-2019-9895 CRITICAL
9.8 Mar 21

In PuTTY versions before 0.71 on Unix, a remotely triggerable buffer overflow exists in any kind of server-to-client for

CVE-2021-36367 HIGH
8.1 Jul 09

PuTTY through 0.75 proceeds with establishing an SSH session even if it has never sent a substantive authentication resp

CVE-2019-9896 HIGH
7.8 Mar 21

In PuTTY versions before 0.71 on Windows, local attackers could hijack the application by putting a malicious help file

CVE-2019-17069 HIGH
7.5 Oct 01

PuTTY before 0.73 might allow remote SSH-1 servers to cause a denial of service by accessing freed memory locations via

CVE-2019-17068 HIGH
7.5 Oct 01

PuTTY before 0.73 mishandles the "bracketed paste mode" protection mechanism, which may allow a session to be affected b

Vendor StatusVendor

SUSE

Severity: Moderate

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy