CVE-2026-48852 json
PuTTY 0.71 before 0.84 has an assertion failure in ECDSA signature verification.
published 2026-05-25 5 mo ago modified 2026-07-24 3 mo ago also EUVD-2026-31735
- cvss
- 3.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
PuTTY 0.71 before 0.84 has an assertion failure in ECDSA signature verification.
Patch / fix
- PuTTY PuTTY 0.84
- putty Debian 14 0.84-1
debian advisories DEBIAN-CVE-2026-48852
- putty openSUSE Leap 16.0 0.85-bp160.1.1
- putty openSUSE Tumbleweed 0.85-2.1
opensuse advisories openSUSE-SU-2026:22127-1openSUSE-SU-2026:12168-1
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-48852 updated cvss 3.7
PuTTY: assertion failure in ECDSA signature verification
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected products
- PuTTY PuTTY
Classification
- Weakness
-
- CWE-617 Reachable Assertion
References
-
chiark.greenend.org.uk
/~sgtatham/putty/wishlist/ecdsa-remotely-triggerable-assertion.html
patch, vendor-advisory
-
lists.tartarus.org
/pipermail/putty-announce/2026/000042.html
release-notes
Sources
- CVE List CVE-2026-48852
- NVD CVE-2026-48852
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.