CVE-2026-115728 @hapi/content 6.0.1 before 6.0.3 ReDoS via Content.disposition() Parameter Parsing
High 8.7
Published
Updated
Check this codebase for CVE-2026-115728 and fix it if it is affected.
What it is: CVE-2026-115728 is a high-severity vulnerability in hapijs @hapi/content, published on 23 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-115728 in the wild and no public exploit code.
Affected product: hapijs @hapi/content. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-115728/ (Markdown: https://insights.sbomify.com/CVE-2026-115728/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-115728?
CVE-2026-115728 is a high-severity vulnerability in hapijs @hapi/content, published on 23 Oct 2026.
Official description
@hapi/content from 6.0.1 before 6.0.3 contains a regular expression denial of service vulnerability in Content.disposition() caused by an incomplete fix for CVE-2026-35213. Unauthenticated remote attackers can send multipart uploads with a long Content-Disposition parameter lacking an equals sign, triggering quadratic backtracking that blocks the event loop.
Weakness: CWE-1333
Which versions are affected by CVE-2026-115728?
How do I fix CVE-2026-115728?
No fix has been published for CVE-2026-115728 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-115728 being exploited?
There is no known exploitation of CVE-2026-115728 in the wild and no public exploit code.
Sources
Also known as GHSA-vwgx-c45f-9873.