Vulnerability Database · npm · body-parser · Version

body-parser 1.8.0

1.8.0 is affected by 3 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 0 High 1 Medium 1 Low 1 Unrated 0

Released 06 Sep 2014 Licence MIT Also known from other sources 2 Newer releases 87 Database updated 23/Oct/2026

Release and licence data published by the npm registry. 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 Vulnerabilities affecting this version

body-parser 1.8.0 vulnerabilities

3 vulnerabilities cover body-parser 1.8.0. Open the full list in the database.

Looking for another version, or everything Vulert holds for body-parser?

All versions → Full vulnerability list →

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 body-parser 1.8.0

Is body-parser 1.8.0 vulnerable?

Yes. 3 vulnerabilities in the Vulert database cover body-parser 1.8.0: 0 critical, 1 high, 1 medium and 1 low. Each entry above names the fixed version to move to.

Is 1.8.0 the latest release of body-parser?

No. 1.8.0 was published 06 Sep 2014, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor body-parser for upcoming vulnerabilities?

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