VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

paste: vulnerability history, versions and safety

paste is a package in the PyPI ecosystem. Vulert records 3 vulnerabilities for it across 74 releases, from Nov 2010 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M1 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

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.

See all paste vulnerabilities

Vulert verdict on paste 3.10.1 i

Updated on 23 Oct 2026

Good news: 3.10.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

Package health score 76/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

What to do: Stay on 3.10.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.10.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.10.1 — unaffected i
  • Vulnerabilities on record 3 over 11 years · 0 in the last year i
  • Latest disclosure 17 May 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 509 packages i
  • Stars 63 i
  • Last release 29 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

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 tracks for paste, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.10.1 01 May 2024 none MIT — Details →
3.10.0 27 Apr 2024 none MIT — Details →
3.9.0 05 Apr 2024 none MIT — Details →
3.8.0 16 Mar 2024 none MIT — Details →
3.7.1 19 Oct 2023 none MIT — Details →
3.6.1 15 Oct 2023 none MIT — Details →
3.6.0 02 Oct 2023 none MIT — Details →
3.5.3 30 Apr 2023 none MIT — Details →
3.5.2 18 Aug 2022 none MIT — Details →
3.5.1 22 Jun 2022 none MIT — Details →
3.5.0 12 Oct 2020 none MIT — Details →
3.4.6 25 Sep 2020 none MIT — Details →
3.4.5 24 Sep 2020 none MIT — Details →
3.4.4 09 Sep 2020 none MIT — Details →
3.4.3 22 Jul 2020 none MIT — Details →
3.4.2 14 Jul 2020 none MIT — Details →
3.4.1 04 Jun 2020 none MIT — Details →
3.4.0 12 Feb 2020 none MIT — Details →
3.3.0 28 Jan 2020 none MIT — Details →
3.2.7 26 Jan 2020 none MIT — Details →
3.2.6 13 Jan 2020 none MIT — Details →
3.2.5 09 Jan 2020 none MIT — Details →
3.2.4 05 Jan 2020 none MIT — Details →
3.2.3 25 Nov 2019 none MIT — Details →
3.2.2 14 Oct 2019 none MIT — Details →
3.2.1 25 Sep 2019 none MIT — Details →
3.2.0 05 Sep 2019 none MIT — Details →
3.1.1 25 Aug 2019 none MIT — Details →
3.1.0 24 Jul 2019 none MIT — Details →
3.0.8 07 Mar 2019 none MIT — Details →
3.0.7 28 Feb 2019 none MIT — Details →
3.0.6 07 Jan 2019 none MIT — Details →
3.0.5 29 Nov 2018 none MIT — Details →
3.0.4 05 Nov 2018 none MIT — Details →
3.0.3 03 Nov 2018 none MIT — Details →
3.0.2 31 Oct 2018 none MIT — Details →
3.0.1 24 Oct 2018 none MIT — Details →
3.0.0 24 Oct 2018 none MIT — Details →
2.0.3 09 Mar 2016 none MIT — Details →
2.0.2 11 May 2015 none MIT — Details →
2.0.1 23 Apr 2015 none MIT — Details →
2.0.0 21 Apr 2015 none MIT — Details →
1.7.5.1 20 Sep 2010 none MIT — Details →
1.7.5 14 Sep 2010 U1 MIT Yes Details →
1.7.4 24 Jun 2010 U1 MIT Yes Details →
1.7.3.1 20 Apr 2010 M1 U2 MIT Yes Details →
1.7.3 31 Mar 2010 M1 U2 MIT Yes Details →
1.7.2 29 Oct 2008 M1 U2 MIT Yes Details →
1.7.1 13 Jun 2008 M1 U2 MIT Yes Details →
1.7.0 20 May 2008 M1 U2 MIT Yes Details →
1.6.0 04 Jan 2008 M1 U2 MIT Yes Details →
1.5.1 23 Oct 2007 M1 U2 MIT Yes Details →
1.5.0 17 Oct 2007 M1 U2 MIT Yes Details →
1.4.2 07 Sep 2007 M1 U2 MIT Yes Details →
1.4.1 04 Sep 2007 M1 U2 MIT Yes Details →
1.4.0 26 Jun 2007 M1 U2 MIT Yes Details →
1.3.0 07 Mar 2007 M1 U2 MIT Yes Details →
1.2.1 01 Feb 2007 M1 U2 MIT Yes Details →
1.2.0 01 Feb 2007 M1 U2 MIT Yes Details →
1.1.1 22 Dec 2006 M1 U2 MIT Yes Details →
1.1.0 18 Dec 2006 M1 U2 MIT Yes Details →
1.0.1 18 Dec 2006 M1 U2 MIT Yes Details →
1.0.0 22 Oct 2006 M1 U2 MIT Yes Details →
0.9.8.1 05 Sep 2006 M1 U2 MIT Yes Details →
0.9.8 04 Sep 2006 M1 U2 MIT Yes Details →
0.9.7 12 Aug 2006 M1 U2 MIT Yes Details →
0.9.6 27 Jul 2006 M1 U2 MIT Yes Details →
0.9.5 20 Jul 2006 M1 U2 MIT Yes Details →
0.9.3 24 May 2006 M1 U2 MIT Yes Details →
0.9.2 15 May 2006 M1 U2 MIT Yes Details →
0.9.1 07 May 2006 M1 U2 MIT Yes Details →
0.9.0 21 Apr 2006 M1 U2 MIT Yes Details →
0.5.0 07 Mar 2006 M1 U2 MIT Yes Details →
0.4.1 18 Jan 2006 M1 U2 MIT Yes Details →
0.4.0 09 Jan 2006 M1 U2 MIT Yes Details →
0.3.0 03 Oct 2005 M1 U2 MIT Yes Details →
0.3-py2.3 — M1 U2 — Yes Details →
0.3-py2.4 — M1 U2 — Yes Details →
0.4-py2.3 — M1 U2 — Yes Details →
0.4-py2.4 — M1 U2 — Yes Details →
0.4.1-py2.3 — M1 U2 — Yes Details →
0.4.1-py2.4 — M1 U2 — Yes Details →
0.5-py2.3 — M1 U2 — Yes Details →
0.5-py2.4 — M1 U2 — Yes Details →
0.9-py2.3 — M1 U2 — Yes Details →
0.9-py2.4 — M1 U2 — Yes Details →
0.9.1-py2.3 — M1 U2 — Yes Details →
0.9.1-py2.4 — M1 U2 — Yes Details →
0.9.2-py2.4 — M1 U2 — Yes Details →
0.9.3-py2.4 — M1 U2 — Yes Details →
0.9.5-py2.3 — M1 U2 — Yes Details →
0.9.5-py2.4 — M1 U2 — Yes Details →
0.9.6-py2.3 — M1 U2 — Yes Details →
0.9.6-py2.4 — M1 U2 — Yes Details →
0.9.7-py2.3 — M1 U2 — Yes Details →
0.9.7-py2.4 — M1 U2 — Yes Details →
0.9.8-py2.3 — M1 U2 — Yes Details →
0.9.8-py2.4 — M1 U2 — Yes Details →
0.9.8.1-py2.3 — M1 U2 — Yes Details →
0.9.8.1-py2.4 — M1 U2 — Yes Details →
1.0-py2.4 — M1 U2 — Yes Details →
1.0.1-py2.4 — M1 U2 — Yes Details →
1.1-py2.4 — M1 U2 — Yes Details →
1.1.1-py2.4 — M1 U2 — Yes Details →
1.2-py2.4 — M1 U2 — Yes Details →
1.2.1-py2.4 — M1 U2 — Yes Details →
1.3-py2.4 — M1 U2 — Yes Details →
1.3-py2.5 — M1 U2 — Yes Details →
1.4-py2.4 — M1 U2 — Yes Details →
1.4.1-py2.4 — M1 U2 — Yes Details →
1.4.2-py2.4 — M1 U2 — Yes Details →
1.5-py2.4 — M1 U2 — Yes Details →
1.5-py2.5 — M1 U2 — Yes Details →
1.5.1-py2.4 — M1 U2 — Yes Details →
1.5.1-py2.5 — M1 U2 — Yes Details →
1.6-py2.4 — M1 U2 — Yes Details →
1.6-py2.5 — M1 U2 — Yes Details →

All 117 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2010 1
  • 2012 1
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for paste

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2010-2477: Cross-site Scripting Vulnerability in Paste 6.1 medium 1.7.4 17 May 2022
... N/A unrated 1.7.4 06 Nov 2010
CVE-2012-0878: Vulnerability in Paste Script N/A unrated 1.7.5.1 01 May 2012

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 paste

Is paste safe to use?

Vulert records 3 vulnerabilities for paste in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is paste's Vulert package health score?

Vulert scores paste 76/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of paste affected?

No. 3.10.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of paste should I use?

3.10.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does paste have?

3 vulnerabilities are recorded for paste in the PyPI ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 2 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 paste vulnerabilities disclosed?

0 vulnerabilities were recorded for paste in the last 12 months, and the oldest entry in this database dates to 06 Nov 2010. 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 paste 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 paste for upcoming vulnerabilities?

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