VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

llhttp: vulnerability history, versions and safety

llhttp is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 1 release, from Jul 2022 to Jul 2023. 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 C2 H1
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 llhttp vulnerabilities

Vulert verdict on llhttp 1.0.1 i

Updated on 23 Oct 2026

Action needed: 1.0.1 has 3 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 61/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 1.0.1 — affected i
  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 01 Jul 2023 i
  • Highest CVSS 9.1 i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Stars 1,950 i
  • OpenSSF scorecard 6/10 i
  • Last release 95 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, 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 llhttp, 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.1 20 Nov 2018 C2 H1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2023 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 llhttp

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-32213: llhttp HTTP Request Smuggling Vulnerability 9.1 critical 6.0.7 15 Jul 2022
CVE-2022-32214: llhttp allows HTTP Request Smuggling via Improper Delimiting of Header Fields 9.1 critical 6.0.7 15 Jul 2022
CVE-2023-30589: llhttp vulnerable to HTTP request smuggling 7.5 high 8.1.1 01 Jul 2023

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 llhttp

Is llhttp safe to use?

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

What is llhttp's Vulert package health score?

Vulert scores llhttp 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 llhttp affected?

Yes. 1.0.1, the version you would install today, has 3 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

How many vulnerabilities does llhttp have?

3 vulnerabilities are recorded for llhttp in the npm ecosystem: 2 critical, 1 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new llhttp vulnerabilities disclosed?

0 vulnerabilities were recorded for llhttp in the last 12 months, and the oldest entry in this database dates to 15 Jul 2022. 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 llhttp 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 llhttp for upcoming vulnerabilities?

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