CVE-2026-48795
Prototype pollution in AdonisJS bodyparser via nested multipart fields.
Is CVE-2026-48795 being exploited?
Not confirmed. CVE-2026-48795 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.55% probability of exploitation in the next 30 days.
How severe is CVE-2026-48795?
CVE-2026-48795 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-48795?
Yes. A fix has been recorded for CVE-2026-48795. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-48795 affect?
CVE-2026-48795 affects @adonisjs/bodyparser v10.1.3-10.1.4, @adonisjs/bodyparser v11.0.0-11.0.2 (AdonisJS). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-48795?
Upgrade to @adonisjs/bodyparser v10.1.5 or v11.0.3; validate/block nested multipart keys.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can pollute Object.prototype via multipart fields, enabling logic bypasses, data corruption, or potentially leading to remote code execution in vulnerable apps.
Immediate action required
- affected>= 10.1.3 and < 10.1.5
- affected>= 11.0.0-next.9 and < 11.0.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.