VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@adonisjs/bodyparser: vulnerability history, versions and safety

@adonisjs/bodyparser is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 104 releases, from Jan 2026 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C1 H3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 30 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all @adonisjs/bodyparser vulnerabilities

Vulert verdict on @adonisjs/bodyparser 11.0.4 i

Updated on 23 Oct 2026

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

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

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

  • Current release 11.0.4 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 4 in the last year i
  • Latest disclosure 30 Jun 2026 i
  • Highest CVSS 9.2 i
  • With no published fix 0 i
  • Depended on by 5 packages i
  • Stars 35 i
  • Last release 4 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 @adonisjs/bodyparser, 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
11.0.4 25 May 2026 none MIT — Details →
10.1.5 22 May 2026 none MIT — Details →
11.0.3 22 May 2026 none MIT — Details →
11.0.2 19 May 2026 none MIT — Details →
11.0.1 04 Apr 2026 none MIT — Details →
11.0.0 25 Feb 2026 none MIT — Details →
10.1.4 23 Feb 2026 H1 MIT Yes Details →
10.1.3 05 Feb 2026 H1 MIT Yes Details →
11.0.0-next.9 05 Feb 2026 none MIT — Details →
11.0.0-next.8 01 Feb 2026 none MIT — Details →
11.0.0-next.7 01 Feb 2026 none MIT — Details →
11.0.0-next.6 02 Jan 2026 none MIT — Details →
10.1.2 02 Jan 2026 H2 MIT Yes Details →
11.0.0-next.5 15 Dec 2025 none MIT — Details →
11.0.0-next.4 03 Dec 2025 none MIT — Details →
11.0.0-next.3 20 Nov 2025 none MIT — Details →
10.1.1 20 Nov 2025 C1 H2 MIT Yes Details →
11.0.0-next.2 25 Oct 2025 none MIT — Details →
11.0.0-next.1 02 Sep 2025 none MIT — Details →
11.0.0-next.0 30 Jul 2025 none MIT — Details →
10.1.0 15 May 2025 C1 H2 MIT Yes Details →
10.0.3 13 Feb 2025 C1 H2 MIT Yes Details →
10.0.2 22 Apr 2024 C1 H2 MIT Yes Details →
10.0.1 23 Jan 2024 C1 H2 MIT Yes Details →
10.0.0 07 Jan 2024 C1 H2 MIT Yes Details →
10.0.0-3 19 Dec 2023 C1 H2 MIT Yes Details →
10.0.0-2 23 Nov 2023 C1 H2 MIT Yes Details →
10.0.0-1 20 Oct 2023 C1 H2 MIT Yes Details →
10.0.0-0 17 Oct 2023 C1 H2 MIT Yes Details →
9.3.2-8 23 Aug 2023 C1 H2 MIT Yes Details →
9.3.2-7 26 Jul 2023 C1 H2 MIT Yes Details →
8.1.9 04 Jul 2023 C1 H2 MIT Yes Details →
9.3.2-6 04 Jul 2023 C1 H2 MIT Yes Details →
8.1.8 06 Jun 2023 C1 H2 MIT Yes Details →
9.3.2-5 14 Apr 2023 C1 H2 MIT Yes Details →
9.3.2-4 27 Mar 2023 C1 H2 MIT Yes Details →
9.3.2-3 15 Mar 2023 C1 H2 MIT Yes Details →
9.3.2-2 14 Mar 2023 C1 H2 MIT Yes Details →
9.3.2-1 11 Mar 2023 C1 H2 MIT Yes Details →
9.3.2-0 04 Mar 2023 C1 H2 MIT Yes Details →
9.3.1-0 03 Mar 2023 C1 H2 MIT Yes Details →
9.3.0-0 14 Feb 2023 C1 H2 MIT Yes Details →
9.2.2-0 13 Feb 2023 C1 H2 MIT Yes Details →
9.2.1-0 11 Feb 2023 C1 H2 MIT Yes Details →
9.2.0-0 03 Feb 2023 C1 H2 MIT Yes Details →
9.1.1-0 30 Jan 2023 C1 H2 MIT Yes Details →
9.1.0-0 27 Jan 2023 C1 H2 MIT Yes Details →
9.0.3-0 23 Jan 2023 C1 H2 MIT Yes Details →
9.0.2-0 17 Jan 2023 C1 H2 MIT Yes Details →
9.0.1-0 17 Jan 2023 C1 H2 MIT Yes Details →
9.0.0-0 12 Jan 2023 C1 H2 MIT Yes Details →
8.1.7 07 Oct 2022 C1 H2 MIT Yes Details →
8.1.6 26 May 2022 C1 H2 MIT Yes Details →
8.1.5 23 May 2022 C1 H2 MIT Yes Details →
8.1.4 09 May 2022 C1 H2 MIT Yes Details →
8.1.3 08 Apr 2022 C1 H2 MIT Yes Details →
8.1.2 05 Apr 2022 C1 H2 MIT Yes Details →
8.1.1 24 Mar 2022 C1 H2 MIT Yes Details →
8.1.0 25 Feb 2022 C1 H2 MIT Yes Details →
8.0.2 17 Jan 2022 C1 H2 MIT Yes Details →
8.0.1 25 Aug 2021 C1 H2 MIT Yes Details →
8.0.0 16 Aug 2021 C1 H2 MIT Yes Details →
7.1.5 27 Jul 2021 C1 H2 MIT Yes Details →
7.1.4 19 Jul 2021 C1 H2 MIT Yes Details →
7.1.3 03 Jul 2021 C1 H2 MIT Yes Details →
7.1.2 02 Jun 2021 C1 H2 MIT Yes Details →
7.1.1 05 May 2021 C1 H2 MIT Yes Details →
7.1.0 24 Apr 2021 C1 H2 MIT Yes Details →
2.3.0 26 Mar 2021 C1 H2 MIT Yes Details →
7.0.1 25 Mar 2021 C1 H2 MIT Yes Details →
7.0.0 22 Mar 2021 C1 H2 MIT Yes Details →
6.0.0 13 Feb 2021 C1 H2 MIT Yes Details →
5.1.0 11 Dec 2020 C1 H2 MIT Yes Details →
5.0.8 10 Dec 2020 C1 H2 MIT Yes Details →
5.0.7 25 Nov 2020 C1 H2 MIT Yes Details →
5.0.6 24 Oct 2020 C1 H2 MIT Yes Details →
5.0.5 20 Oct 2020 C1 H2 MIT Yes Details →
5.0.4 13 Oct 2020 C1 H2 MIT Yes Details →
5.0.3 10 Oct 2020 C1 H2 MIT Yes Details →
5.0.2 01 Oct 2020 C1 H2 MIT Yes Details →
5.0.1 27 Sep 2020 C1 H2 MIT Yes Details →
5.0.0 25 Sep 2020 C1 H2 MIT Yes Details →
4.0.6 28 Aug 2020 C1 H2 MIT Yes Details →
4.0.5 26 Jul 2020 C1 H2 MIT Yes Details →
4.0.4 18 Jun 2020 C1 H2 MIT Yes Details →
4.0.3 14 May 2020 C1 H2 MIT Yes Details →
4.0.2 14 Apr 2020 C1 H2 MIT Yes Details →
4.0.1 13 Apr 2020 C1 H2 MIT Yes Details →
4.0.0 12 Apr 2020 C1 H2 MIT Yes Details →
3.2.7 03 Mar 2020 C1 H2 MIT Yes Details →
3.2.6 01 Mar 2020 C1 H2 MIT Yes Details →
3.2.5 27 Feb 2020 C1 H2 MIT Yes Details →
3.2.4 15 Feb 2020 C1 H2 MIT Yes Details →
3.2.3 14 Feb 2020 C1 H2 MIT Yes Details →
3.2.2 10 Feb 2020 C1 H2 MIT Yes Details →
3.2.1 08 Feb 2020 C1 H2 MIT Yes Details →
3.2.0 04 Jan 2020 C1 H2 MIT Yes Details →
3.1.0 24 Dec 2019 C1 H2 MIT Yes Details →
3.0.16 25 Nov 2019 C1 H2 MIT Yes Details →
3.0.15 11 Nov 2019 C1 H2 MIT Yes Details →
3.0.14 20 Sep 2019 C1 H2 — Yes Details →
3.0.13 09 Sep 2019 C1 H2 — Yes Details →
3.0.12 04 Sep 2019 C1 H2 — Yes Details →
3.0.11 02 Sep 2019 C1 H2 — Yes Details →
3.0.10 30 Aug 2019 C1 H2 — Yes Details →
3.0.9 28 Aug 2019 C1 H2 — Yes Details →
3.0.8 27 Aug 2019 C1 H2 — Yes Details →
3.0.7 19 Aug 2019 C1 H2 — Yes Details →
3.0.6 31 Jul 2019 C1 H2 — Yes Details →
3.0.5 31 Jul 2019 C1 H2 — Yes Details →
3.0.4 31 Jul 2019 C1 H2 — Yes Details →
3.0.3 10 Jul 2019 C1 H2 — Yes Details →
3.0.2 29 Jun 2019 C1 H2 — Yes Details →
3.0.1 29 Jun 2019 C1 H2 — Yes Details →
3.0.0 24 May 2019 C1 H2 — Yes Details →
2.2.5 04 May 2019 C1 H2 — Yes Details →
2.2.4 25 Apr 2019 C1 H2 — Yes Details →
2.2.3 24 Apr 2019 C1 H2 — Yes Details →
2.2.2 03 Apr 2019 C1 H2 — Yes Details →
2.2.1 25 Mar 2019 C1 H2 — Yes Details →

The newest 120 of 143 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for @adonisjs/bodyparser

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Path Traversal Vulnerability in @adonisjs/bodyparser 9.2 critical 10.1.2 02 Jan 2026
CVE-2026-48795: @adonisjs/bodyparser Incomplete Fix Allows Prototype Pollution 8.6 high 10.1.5 30 Jun 2026
CVE-2026-25762: Denial of Service Vulnerability in @adonisjs/bodyparser Due to Unrestricted Memory Buffering 7.5 high 10.1.3 06 Feb 2026
CVE-2026-25754: AdonisJS BodyParser Prototype Pollution Vulnerability 7.2 high 10.1.3 06 Feb 2026

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 @adonisjs/bodyparser

Is @adonisjs/bodyparser safe to use?

Vulert records 4 vulnerabilities for @adonisjs/bodyparser in npm: 1 critical, 3 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 @adonisjs/bodyparser's Vulert package health score?

Vulert scores @adonisjs/bodyparser 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 @adonisjs/bodyparser affected?

No. 11.0.4, 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 @adonisjs/bodyparser should I use?

11.0.4 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 @adonisjs/bodyparser have?

4 vulnerabilities are recorded for @adonisjs/bodyparser in the npm ecosystem: 1 critical, 3 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 @adonisjs/bodyparser vulnerabilities disclosed?

4 vulnerabilities were recorded for @adonisjs/bodyparser in the last 12 months, and the oldest entry in this database dates to 02 Jan 2026. 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 @adonisjs/bodyparser 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 @adonisjs/bodyparser for upcoming vulnerabilities?

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