VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

roundup: vulnerability history, versions and safety

roundup is a package in the PyPI ecosystem. Vulert records 30 vulnerabilities for it across 82 releases, from Mar 2008 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
30 vulnerabilities recorded C1 M14 U15
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 02 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all roundup vulnerabilities

Vulert verdict on roundup 2.6.0 i

Updated on 23 Oct 2026

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

Package health score 61/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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

  • Current release 2.6.0 — unaffected i
  • Vulnerabilities on record 30 over 18 years · 2 in the last year i
  • Latest disclosure 02 Jul 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Last release 3 months ago i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 roundup, 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
2.6.0 13 Jul 2026 none — — Details →
2.6.0b1 03 Jun 2026 none non-standard — Details →
2.5.0 13 Jul 2025 none non-standard — Details →
2.5.0b1 11 Jun 2025 M1 U1 non-standard Yes Details →
2.4.0 13 Jul 2024 M1 U1 non-standard Yes Details →
2.4.0b2 28 May 2024 M4 U4 non-standard Yes Details →
2.4.0b1 27 May 2024 M4 U4 non-standard Yes Details →
2.3.0 13 Jul 2023 M4 U4 non-standard Yes Details →
2.3.0b2 31 May 2023 M4 U4 non-standard Yes Details →
2.2.0 13 Jul 2022 M4 U4 non-standard Yes Details →
2.2.0b1 15 Jun 2022 M4 U4 MIT Yes Details →
2.1.0 13 Jul 2021 M4 U4 MIT Yes Details →
2.1.0b1 19 Jun 2021 M4 U4 MIT Yes Details →
2.0.0 13 Jul 2020 M4 U4 MIT Yes Details →
2.0.0b0 06 Apr 2020 M4 U5 MIT Yes Details →
2.0.0a0 23 Oct 2019 M4 U5 MIT Yes Details →
1.6.1 13 Jul 2019 M5 U5 MIT Yes Details →
1.6.0 13 Jul 2018 M5 U5 MIT Yes Details →
1.5.1 11 Jan 2016 M5 U5 MIT Yes Details →
1.5.0 06 Jul 2013 M6 U6 MIT Yes Details →
1.4.21 21 Dec 2012 M6 U6 MIT Yes Details →
1.4.20 15 May 2012 M6 U6 non-standard Yes Details →
1.4.19 15 Jul 2011 M10 U10 non-standard Yes Details →
1.4.18 29 May 2011 M10 U10 non-standard Yes Details →
1.4.17 13 May 2011 M10 U10 non-standard Yes Details →
1.4.16 08 Oct 2010 M10 U10 non-standard Yes Details →
1.4.15 12 Jul 2010 M10 U10 non-standard Yes Details →
1.4.14 01 Jul 2010 M10 U10 non-standard Yes Details →
1.4.13 19 Feb 2010 M11 U11 non-standard Yes Details →
1.4.12 09 Feb 2010 M11 U11 non-standard Yes Details →
1.4.11 21 Dec 2009 M11 U11 non-standard Yes Details →
1.4.10 12 Oct 2009 M11 U11 non-standard Yes Details →
1.4.9 10 Aug 2009 M11 U11 non-standard Yes Details →
1.4.8 18 Mar 2009 M11 U11 non-standard Yes Details →
1.4.7 13 Mar 2009 M11 U11 non-standard Yes Details →
1.4.6 01 Sep 2008 M11 U12 non-standard Yes Details →
1.4.5.1 19 Aug 2008 M11 U12 non-standard Yes Details →
1.4.4 01 Mar 2008 C1 M11 U13 non-standard Yes Details →
1.4.3 27 Feb 2008 C1 M12 U14 non-standard Yes Details →
1.4.2 10 Feb 2008 C1 M12 U14 non-standard Yes Details →
1.4.1 07 Nov 2007 C1 M12 U14 non-standard Yes Details →
1.4.0 04 Nov 2007 C1 M12 U14 non-standard Yes Details →
1.3.3 15 Feb 2007 C1 M12 U13 non-standard Yes Details →
1.3.2 19 Dec 2006 C1 M12 U13 non-standard Yes Details →
1.3.1 11 Nov 2006 C1 M12 U13 non-standard Yes Details →
1.3.0 09 Nov 2006 C1 M12 U13 non-standard Yes Details →
1.2.1 07 Oct 2006 C1 M12 U13 non-standard Yes Details →
1.2.0 04 Oct 2006 C1 M13 U14 non-standard Yes Details →
1.1.2 27 Apr 2006 C1 M12 U13 non-standard Yes Details →
0.6.11 16 Mar 2006 C1 M13 U14 non-standard Yes Details →
1.1.1 03 Mar 2006 C1 M12 U13 non-standard Yes Details →
1.1.0 10 Feb 2006 C1 M12 U13 non-standard Yes Details →
1.0.1 03 Feb 2006 C1 M12 U13 non-standard Yes Details →
1.0.0 27 Jan 2006 C1 M12 U13 non-standard Yes Details →
0.8.6 27 Jan 2006 C1 M12 U13 non-standard Yes Details →
0.8.5 07 Oct 2005 C1 M12 U13 non-standard Yes Details →
0.9.0b1 07 Oct 2005 C1 M12 U13 non-standard Yes Details →
0.8.4 18 Jul 2005 C1 M12 U13 non-standard Yes Details →
0.8.3 02 May 2005 C1 M12 U13 non-standard Yes Details →
0.7.12 02 May 2005 C1 M12 U13 non-standard Yes Details →
0.8.2 22 Mar 2005 C1 M12 U13 non-standard Yes Details →
0.8.2.win32 — C1 M12 U13 — Yes Details →
0.8.4.win32 — C1 M12 U13 — Yes Details →
1.0.1.win32 — C1 M12 U13 — Yes Details →
1.1.0.win32 — C1 M12 U13 — Yes Details →
1.1.1.win32 — C1 M12 U13 — Yes Details →
1.1.2.win32 — C1 M12 U13 — Yes Details →
1.3.0.win32 — C1 M12 U13 — Yes Details →
1.3.1.win32 — C1 M12 U13 — Yes Details →
1.3.2.win32 — C1 M12 U13 — Yes Details →
1.3.3.win32 — C1 M12 U13 — Yes Details →
1.4.0.win32 — C1 M12 U13 — Yes Details →
1.4.1.win32 — C1 M12 U13 — Yes Details →
1.4.10.win32 — M11 U11 — Yes Details →
1.4.17.win32 — M10 U10 — Yes Details →
1.4.18.win32 — M10 U10 — Yes Details →
1.4.19.win32 — M10 U10 — Yes Details →
1.4.20.win32 — M10 U10 — Yes Details →
1.4.21.win32 — M6 U6 — Yes Details →
1.4.5.1.win32 — M11 U11 — Yes Details →
1.4.6.win32 — M11 U11 — Yes Details →
1.4.7.win32 — M11 U11 — Yes Details →
1.4.8.win32 — M11 U11 — Yes Details →
1.5.0.win32 — M6 U6 — Yes Details →
1.5.1.win32 — M6 U6 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2008 2
  • 2010 1
  • 2014 3
  • 2016 1
  • 2019 2
  • 2020 1
  • 2022 10
  • 2024 6
  • 2025 2
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for roundup

The 5 most severe of 30 vulnerabilities recorded for this package

Search all 30 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2008-1475: Roundup xml-rpc server improper check of property permissions 9.1 critical 1.4.5 01 May 2022
CVE-2025-53865: Roundup Package Vulnerable to XSS via URL and Template Interaction 6.4 medium 2.5.0 13 Jul 2025
CVE-2012-6133: Cross-Site Scripting (XSS) Vulnerabilities in Roundup 6.1 medium 1.4.20 23 Apr 2022
CVE-2019-10904: XSS Vulnerability in Roundup 6.1 medium 2.0.0alpha0 09 Apr 2019
CVE-2008-1474: Roundup Cross-site Scripting (XSS) Vulnerability 6.1 medium 1.4.4 01 May 2022

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 roundup

Is roundup safe to use?

Vulert records 30 vulnerabilities for roundup in PyPI: 1 critical, 0 high, 14 medium and 0 low, plus 15 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 roundup's Vulert package health score?

Vulert scores roundup 61/100, which reads as usable, but worth attention. 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 roundup affected?

No. 2.6.0, 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 roundup should I use?

2.6.0 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 roundup have?

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

2 vulnerabilities were recorded for roundup in the last 12 months, and the oldest entry in this database dates to 24 Mar 2008. 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 roundup 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 roundup for upcoming vulnerabilities?

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