CVE-2026-48795

HIGHPre-NVD 8.68.6
EchelonGraph scoreLOW confidence

This high-severity CVE scores 8.6 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m
8.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: —CVSS: 8.6Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

@adonisjs/bodyparser has an incomplete fix for CVE-2026-25754

Summary

The fix for GHSA-f5x2-vj4h-vg4c / CVE-2026-25754 introduced in commit 40e1c71 is incomplete and can be bypassed through nested prototype pollution payloads.

The original patch replaced the internal FormFields storage object with Object.create(null), preventing direct payloads such as __proto__.polluted. However, payloads containing a non-dangerous segment before __proto__ or constructor.prototype, such as user.__proto__.polluted, still lead to Object.prototype pollution.

This issue is exploitable remotely through a single unauthenticated multipart/form-data request using the default configuration.

Affected versions

  • >= 10.1.3 < 10.1.5
  • >= 11.0.0-next.9 < 11.0.3

Details

The regression tests added by the original fix only covered direct payloads such as:

  • __proto__.polluted
  • constructor.prototype.polluted

These payloads are blocked because the root object no longer inherits from Object.prototype.

However, lodash _.set() (via @poppinss/utils) still creates intermediate objects using plain {} values. Once a normal segment is encountered, subsequent __proto__ or constructor.prototype segments regain access to Object.prototype.

Impact

An unauthenticated attacker can remotely pollute Object.prototype on any route accepting multipart/form-data requests behind BodyParserMiddleware.

Because the pollution is process-wide, the impact may include authorization bypasses, unexpected behavior in downstream libraries, or prototype pollution gadget chains leading to remote code execution.

Patches

Fixes targeting v6 and v7 have been published below.

Users should upgrade to a version that includes the following fix:

  • https://github.com/adonisjs/bodyparser/releases/tag/v10.1.5
  • https://github.com/adonisjs/bodyparser/releases/tag/v11.0.3

References

CVSS v3
8.6
EG Score
8.6(low)
EPSS
—
KEV
Not listed

Published

June 30, 2026

Last Modified

June 30, 2026

Vendor Advisories for CVE-2026-48795(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 13× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 07:27 UTCEG score recompute
  2. 2026-07-06 18:27 UTCEG score recompute
  3. 2026-07-06 05:27 UTCEG score recompute
  4. 2026-07-05 16:26 UTCEG score recompute
  5. 2026-07-05 03:24 UTCEG score recompute
  6. 2026-07-04 14:24 UTCEG score recompute
  7. 2026-07-04 01:25 UTCEG score recompute
  8. 2026-07-03 12:28 UTCEG score recompute
  9. 2026-07-02 23:23 UTCEG score recompute
  10. 2026-07-02 10:25 UTCEG score recompute
  11. 2026-07-01 21:27 UTCEG score recompute
  12. 2026-07-01 08:29 UTCEG score recompute
  13. 2026-06-30 19:31 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-48795?
CVE-2026-48795 is a high vulnerability published on June 30, 2026. @adonisjs/bodyparser has an incomplete fix for CVE-2026-25754 Summary The fix for GHSA-f5x2-vj4h-vg4c / CVE-2026-25754 introduced in commit 40e1c71 is incomplete and can be bypassed through nested prototype pollution payloads. The original patch replaced the internal FormFields storage object with…
When was CVE-2026-48795 disclosed?
CVE-2026-48795 was first published in the National Vulnerability Database on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-48795?
CVE-2026-48795 has a CVSS v4.0 base score of 8.6 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-48795?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48795, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-48795

Explore →

Is Your Infrastructure Affected by CVE-2026-48795?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs