VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

meinheld: vulnerability history, versions and safety

meinheld is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 39 releases, from May 2020 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
2 vulnerabilities recorded M1 U1
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 meinheld vulnerabilities

Vulert verdict on meinheld 1.0.2 i

Updated on 23 Oct 2026

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

Package health score 58/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Inactive

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

  • Current release 1.0.2 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 4 packages i
  • Stars 1,456 i
  • OpenSSF scorecard 1/10 i
  • Last release 77 months ago i
  • Licence non-standard 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 meinheld, 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
1.0.2 17 May 2020 none non-standard — Details →
1.0.1 13 May 2019 M1 U1 non-standard Yes Details →
1.0.0 13 May 2019 M1 U1 non-standard Yes Details →
0.6.1 01 Nov 2016 M1 U1 non-standard Yes Details →
0.6.0 19 Oct 2016 M1 U1 non-standard Yes Details →
0.5.9 04 Mar 2016 M1 U1 non-standard Yes Details →
0.5.8 16 Sep 2015 M1 U1 non-standard Yes Details →
0.5.7 17 Dec 2014 M1 U1 non-standard Yes Details →
0.5.6 26 Mar 2014 M1 U1 non-standard Yes Details →
0.5.5 09 Apr 2013 M1 U1 non-standard Yes Details →
0.5.4 10 Mar 2013 M1 U1 non-standard Yes Details →
0.5.3 30 Dec 2012 M1 U1 non-standard Yes Details →
0.5.2 17 Oct 2012 M1 U1 non-standard Yes Details →
0.5.1 10 Oct 2012 M1 U1 non-standard Yes Details →
0.5.0 02 Oct 2012 M1 U1 non-standard Yes Details →
0.4.15 09 Jun 2012 M1 U1 non-standard Yes Details →
0.4.14 06 Jun 2012 M1 U1 non-standard Yes Details →
0.4.13 19 Apr 2011 M1 U1 non-standard Yes Details →
0.4.12 22 Mar 2011 M1 U1 non-standard Yes Details →
0.4.11 21 Mar 2011 M1 U1 non-standard Yes Details →
0.4.10 07 Feb 2011 M1 U1 non-standard Yes Details →
0.4.9 03 Feb 2011 M1 U1 non-standard Yes Details →
0.4.8 19 Jan 2011 M1 U1 non-standard Yes Details →
0.4.7 22 Oct 2010 M1 U1 non-standard Yes Details →
0.4.6 20 Oct 2010 M1 U1 non-standard Yes Details →
0.4.5 17 Oct 2010 M1 U1 non-standard Yes Details →
0.4.4 16 Oct 2010 M1 U1 non-standard Yes Details →
0.4.3 09 Oct 2010 M1 U1 non-standard Yes Details →
0.4.2 23 Sep 2010 M1 U1 non-standard Yes Details →
0.4.1 18 Sep 2010 M1 U1 non-standard Yes Details →
0.4.0 09 Sep 2010 M1 U1 non-standard Yes Details →
0.3.3 06 Sep 2010 M1 U1 non-standard Yes Details →
0.3.2 30 Aug 2010 M1 U1 non-standard Yes Details →
0.3.1 24 Aug 2010 M1 U1 non-standard Yes Details →
0.3.0 23 Aug 2010 M1 U1 non-standard Yes Details →
0.2.1 21 Aug 2010 M1 U1 non-standard Yes Details →
0.2.0 13 Aug 2010 M1 U1 non-standard Yes Details →
0.1.2 03 Aug 2010 M1 U1 non-standard Yes Details →
0.1.1 02 Aug 2010 M1 U1 non-standard Yes Details →
0.1.0 30 Jul 2010 M1 U1 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for meinheld

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-7658: meinheld vulnerable to HTTP Request Smuggling 6.1 medium 1.0.2 24 May 2022
CVE-2020-7658: meinheld HTTP Request Smuggling Vulnerability N/A unrated 1.0.2 22 May 2020

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 meinheld

Is meinheld safe to use?

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

Vulert scores meinheld 58/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 meinheld affected?

No. 1.0.2, 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 meinheld should I use?

1.0.2 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 meinheld have?

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

0 vulnerabilities were recorded for meinheld in the last 12 months, and the oldest entry in this database dates to 22 May 2020. 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 meinheld 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 meinheld for upcoming vulnerabilities?

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