VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

putty: vulnerability history, versions and safety

putty is a package in the Debian ecosystem. Vulert records 34 vulnerabilities for it across 25 releases, from Nov -0001 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
34 vulnerabilities recorded U34
i
4 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 25 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all putty vulnerabilities

Vulert verdict on putty i

Updated on 23 Oct 2026

Careful: 4 of the 34 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 34 vulnerabilities on record across 2026 years, 3 in the last year.

What to do: Plan around the 4 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 34 over 2026 years · 3 in the last year i
  • Latest disclosure 25 May 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 4 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for putty, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 25 of 25 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 1
  • 2003 4
  • 2004 2
  • 2005 4
  • 2007 2
  • 2013 2
  • 2015 4
  • 2016 2
  • 2017 1
  • 2019 6
  • 2020 1
  • 2021 1
  • 2023 1
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 34 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for putty

The 5 most severe of 34 vulnerabilities recorded for this package

Search all 34 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Stack-Based Buffer Overflow in PuTTY SCP Utility 9.8 critical 0.67-1 07 Apr 2016
Critical ECDSA Signature Verification Flaw in PuTTY Package 3.7 low No fix published 25 May 2026
Critical Double Free Vulnerability in PuTTY Package - CVE-2026-48850 3.7 low No fix published 25 May 2026
PuTTY Trust Status Vulnerability - CVE-2026-48851 3.1 low No fix published 25 May 2026
Sensitive Information Exposure in PuTTY due to Inadequate Memory Wiping N/A unrated 0.63-10 27 Mar 2015

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About putty

Is putty safe to use?

Vulert records 34 vulnerabilities for putty in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 34 not yet rated. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does putty have?

34 vulnerabilities are recorded for putty in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 34 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new putty vulnerabilities disclosed?

3 vulnerabilities were recorded for putty in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of putty are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor putty for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the putty version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.