Vulnerability Database · Ubuntu · Package report

python2.7: vulnerability history, versions and safety

python2.7 is a package in the Ubuntu ecosystem. Vulert records 58 vulnerabilities for it across 38 releases, from Aug 2007 to Sep 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
58 vulnerabilities recorded U58
i
11 with no fix published

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

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

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on python2.7 i

Updated on 23 Oct 2026

Careful: 11 of the 58 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 58 vulnerabilities on record across 18 years, none in the last year.

What to do: Plan around the 11 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 58 over 18 years · 0 in the last year i
  • Latest disclosure 29 Sep 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 11 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 python2.7, 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 38 of 38 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2007 1
  • 2014 2
  • 2018 1
  • 2019 10
  • 2020 3
  • 2021 4
  • 2022 8
  • 2023 11
  • 2024 10
  • 2025 8

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

03 Vulnerabilities

Recorded vulnerabilities for python2.7

The 5 most severe of 58 vulnerabilities recorded for this package

Search all 58 in the database →

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 python2.7

Is python2.7 safe to use?

Vulert records 58 vulnerabilities for python2.7 in Ubuntu: 0 critical, 0 high, 0 medium and 0 low, plus 58 not yet rated. 11 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does python2.7 have?

58 vulnerabilities are recorded for python2.7 in the Ubuntu ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 58 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 python2.7 vulnerabilities disclosed?

0 vulnerabilities were recorded for python2.7 in the last 12 months, and the oldest entry in this database dates to 28 Aug 2007. 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 python2.7 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 python2.7 for upcoming vulnerabilities?

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