Skip to content
Fencer Vulns
low 3.1

CVE-2026-48851 json

PuTTY 0.77 before 0.84 uses a copy of the PuTTY icon as a trust indication for TELNET data but the trust status is not cleared between prox…

published 2026-05-25 5 mo ago modified 2026-07-24 3 mo ago also EUVD-2026-31731

cvss
3.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

Summary

PuTTY 0.77 before 0.84 uses a copy of the PuTTY icon as a trust indication for TELNET data but the trust status is not cleared between proxy authentication and the main session.

Patch / fix

  • PuTTY PuTTY 0.84
  • putty Debian 14 0.84-1

debian advisories DEBIAN-CVE-2026-48851

  • 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-48851 updated cvss 3.1

PuTTY: TELNET session data is marked with trust sigils after authenticating to a proxy

  • Red Hat All currently supported Red Hat products
    not 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.22% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N

Affected products

  • PuTTY PuTTY

Classification

Weakness
  • CWE-451 User Interface (UI) Misrepresentation of Critical Information

References

Sources

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.