CVE-2026-115728
ReDoS in @hapi/content Content.disposition allows unauthenticated DoS via crafted multipart uploads
Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2026-115728 being exploited?
Not confirmed. CVE-2026-115728 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.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-115728?
CVE-2026-115728 is rated High with a CVSS score of 8.7. 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-115728?
Yes. A fix has been recorded for CVE-2026-115728. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-115728 affect?
CVE-2026-115728 affects @hapi/content 6.0.1 - before 6.0.3, Node.js applications using hapi/content, Hapi-based web services. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-115728?
Upgrade @hapi/content to v6.0.3; limit header/body sizes and add WAF rules
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can trigger quadratic regex backtracking in Content.disposition, blocking the Node.js event loop and causing denial-of-service.
Patch when possible
- affected>= 6.0.1 and < 6.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.