CVE-2026-104269
ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. From 3.0.0 until 3.0.17, ModSecurity's multipart parser does not apply the RFC 2231 filename* parameter precedence used by common Go, Python, Node.js, and Java application parsers. A Content-Disposition header can provide a benign filename parameter for ModSecurity and a different encoded filename* value that the backend prefers, causing MULTIPART_FILENAME rules and the application to make security decisions on different names. Applications that use the backend-selected name for storage, extension checks, or content-type inference can therefore receive a filename that bypassed WAF inspection. PHP's native multipart parser is not affected by this discrepancy. This issue is fixed in version 3.0.17.
Am I affected?
Sign in and add the software you use to your watchlist: we check it against every new vulnerability.
Show me how to fix itTimeline
- Published by NVD
- First covered by RedTeamDaily
- Last updated by NVD
Coverage
ModSecurity WAF Flaws Allow Upload Filter Bypass and Possible Code Execution
Two high-severity flaws in the open-source ModSecurity web application firewall could allow filter bypass and possible remote code execution. CVE-2026-104269 lets an unauthenticated attacker send an upload with both a plain and an RFC 2231 encoded filename, so the WAF sees a harmless file while some backends save a .php file; no patched version is listed. CVE-2026-73857 is a memory-handling flaw that is reachable only when SecParseXmlIntoArgs is On or OnlyArgs.
Sources: NVD and CISA known exploited vulnerabilities catalogue.