Upload-filter bypass via duplicate header parameters
Published Jul 17, 2026 · Updated Jul 17, 2026
Parameter smuggling in @hapi/content before 6.0.2 allows remote attackers to bypass upload filename filters with duplicate header parameters. Content.disposition() retained the last duplicate value, while Content.type() retained the first duplicate charset or boundary rather than rejecting conflicts. Exploitation requires another request-processing component to select the opposite duplicate, allowing a disallowed upload filename to reach downstream handling.
Summary
What happened
Parameter smuggling in @hapi/content before 6.0.2 allows remote attackers to bypass upload filename filters with duplicate header parameters. Content.disposition() retained the last duplicate value, while Content.type() retained the first duplicate charset or boundary rather than rejecting conflicts. Exploitation requires another request-processing component to select the opposite duplicate, allowing a disallowed upload filename to reach downstream handling.
The record
- CVE
- CVE-2026-44974
- Published
- Jul 17, 2026
- Updated
- Jul 17, 2026
- Vendor
- hapi
- Product
- @hapi/content
- Classifications
- CWE-436, CAPEC-34, CAPEC-105, CAPEC-273, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 17, 2026CVE publishedPublication date reported by the CVE source.
- Jul 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 6.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Duplicate-filename Content-Disposition exampleproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo