Servers and applications
CVE-2026-104269
RFC 2231 `filename*` Parameter Bypasses Multipart Filename Rules on RFC-Compliant Backends (Go, Python, Node, Java)
- Severity
- High 8.6
- Published
- 30 Sept 2026
- Last changed
- 9 Nov 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 3.0.17
- Exploit chance
- 0.6% in the next 30 daysHigher than 47% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- CWE-436
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Change data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N- Also known as
- GHSA-5pww-8rfg-9crf
- Sources
- CVE Program, Project advisories (GitHub)
Description
OWASP CRS multipart filename-inspection rules (CRS rule 920120, 922100, 922110, etc.) extract the filename from the Content-Disposition header using regex or ModSecurity's MULTIPART_NAME / MULTIPART_FILENAME variables. These operate on the raw header bytes as parsed by ModSecurity's multipart parser.
ModSecurity's multipart parser does not implement RFC 2231 (MIME parameter value extensions — language/charset encoded parameters using name*=charset''value syntax). RFC-compliant application parsers do, and when both filename and filename* are present in a Content-Disposition, they prefer the RFC 2231 decoded value of filename* over the plain filename. This is not a Go-specific quirk — it is the behaviour of every mainstream server-side multipart parser that implements the RFC:
Go's mime.ParseMediaType is used as the primary reference below because its stdlib source is compact and unambiguous, but the bypass applies identically to the Python, Node, and Java backends above.
Affected software
| Software | Affected versions |
|---|---|
ModSecurityServers and applications · cna:owasp-modsecurity|modsecurity |
|
ModSecurityServers and applications · github:owasp-modsecurity/modsecurity |
|
About ModSecurity
web application firewall (WAF) module
- Docker Hub pulls
- 7,086,565Docker Hub, 15 Nov 2026
- GitHub stars
- 9,872GitHub, 15 Nov 2026
- Forks
- 1,761GitHub, 15 Nov 2026
- Latest release
- v3.0.17GitHub, 15 Nov 2026
- Released
- 29 Sept 2026GitHub
- Developer
- Trustwave HoldingsWikidata
- License
- Apache Software License 2.0Wikidata
- Written in
- CWikidata
- First published on GitHub
- 2 Feb 2011GitHub
Website Source code Docker image
Vulnerabilities in ModSecurity
- In our list
- 36
- Published in the last 12 months
- 12
- Critical, last 12 months
- 0
- High, last 12 months
- 6
- Known exploited
- 0
- CVE-2026-61813ModSecurity: Incorrect libcurl TLS hostname verification setting in HttpsClient::downloadLow 3.7 5 Nov 2026
- GHSA-4j47-8qcr-jf59`t:base64DecodeExt` silently discards the entire decoded value on a malformed base64 padding group, bypassing rule matchingMedium 5.8 30 Sept 2026
- CVE-2026-104259removeComments Transformation Fails to Strip Adjacent Comments, Enabling WAF Rule BypassMedium 5.4 30 Sept 2026
- CVE-2026-103932PCRE2 `@rxGlobal` match-limit errors are converted to no-matchMedium 5.8 30 Sept 2026
- CVE-2026-73857ModSecurity v3 XML Request Body Processor Uninitialized Pointer Dereference VulnerabilityHigh 7.5 30 Sept 2026
- CVE-2026-73856Response Body Inspection BypassHigh 8.6 30 Sept 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-104269
- GitHub Advisory Database https://github.com/advisories/GHSA-5pww-8rfg-9crf
- github.com https://github.com/owasp-modsecurity/ModSecurity/security/advisories/GHSA-5pww-8rfg-9crf