VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

feedparser: vulnerability history, versions and safety

feedparser is a package in the PyPI ecosystem. Vulert records 10 vulnerabilities for it across 6 releases, from Apr 2011 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
10 vulnerabilities recorded H2 M3 U5
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 feedparser vulnerabilities

Vulert verdict on feedparser 6.0.14 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 6.0.14 — unaffected i
  • Vulnerabilities on record 10 over 11 years · 0 in the last year i
  • Latest disclosure 02 May 2022 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 2,022 packages i
  • Stars 2,445 i
  • OpenSSF scorecard 3/10 i
  • Last release 2 months ago i
  • Licence BSD-2-Clause 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 feedparser, 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
6.0.14 30 Jul 2026 none BSD-2-Clause — Details →
6.0.13 28 Jul 2026 none BSD-2-Clause — Details →
6.0.12 10 Sep 2025 none BSD-2-Clause — Details →
6.0.11 10 Dec 2023 none BSD-2-Clause — Details →
6.0.10 21 May 2022 none BSD-2-Clause — Details →
6.0.9 19 May 2022 none BSD-2-Clause — Details →
6.0.8 22 Jun 2021 none BSD-2-Clause — Details →
6.0.7 22 Jun 2021 none BSD-2-Clause — Details →
6.0.6 15 Jun 2021 none BSD-2-Clause — Details →
6.0.5 14 Jun 2021 none BSD-2-Clause — Details →
6.0.4 13 Jun 2021 none BSD-2-Clause — Details →
6.0.3 13 Jun 2021 none BSD-2-Clause — Details →
6.0.2 25 Oct 2020 none BSD-2-Clause — Details →
6.0.1 15 Sep 2020 none BSD-2-Clause — Details →
6.0.0 12 Sep 2020 none BSD-2-Clause — Details →
6.0.0b3 25 Feb 2020 none BSD-2-Clause — Details →
6.0.0b2 23 Feb 2020 none BSD-2-Clause — Details →
6.0.0b1 02 Oct 2019 none non-standard — Details →
5.2.1 24 Jul 2015 none non-standard — Details →
5.1.3 09 Dec 2012 none non-standard — Details →
5.1.2 03 May 2012 none non-standard — Details →
5.1.1 20 Mar 2012 H1 U1 non-standard Yes Details →
5.1.0 03 Dec 2011 H1 U1 non-standard Yes Details →
5.0.1 20 Feb 2011 H1 U1 non-standard Yes Details →
5.0.0 28 Jan 2011 H2 M2 U4 non-standard Yes Details →
4.1.0 15 Jun 2007 H2 M1 U5 non-standard Yes Details →
4.1-py2.4 — H2 M1 U5 — Yes Details →
5.2.0.post1 — none non-standard — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2011 4
  • 2012 1
  • 2018 4
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for feedparser

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2011-1156: Vulnerability in feedparser 7.5 high 5.0.1 23 Jul 2018
CVE-2012-2921: Vulnerability in feedparser 7.5 high 5.1.2 24 Jul 2018
CVE-2011-1157: Cross-Site Scripting Vulnerability in feedparser 6.1 medium 5.0.1 23 Jul 2018
CVE-2011-1158: Cross-Site Scripting Vulnerability in feedparser 6.1 medium 5.0.1 23 Jul 2018
CVE-2009-5065: Cross-site Scripting Vulnerability in feedparser 6.1 medium 5.0 02 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 feedparser

Is feedparser safe to use?

Vulert records 10 vulnerabilities for feedparser in PyPI: 0 critical, 2 high, 3 medium and 0 low, plus 5 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 feedparser's Vulert package health score?

Vulert scores feedparser 78/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 feedparser affected?

No. 6.0.14, 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 feedparser should I use?

6.0.14 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 feedparser have?

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

0 vulnerabilities were recorded for feedparser in the last 12 months, and the oldest entry in this database dates to 11 Apr 2011. 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 feedparser 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 feedparser for upcoming vulnerabilities?

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