ModSecurity WAF Flaws Allow Upload Filter Bypass and Possible Code Execution
- Severity
- High
- Highest CVSS
- 8.6
- Exploited
- Not known
- Sources
- 1
What happened
CVE-2026-104269 (GHSA-5pww-8rfg-9crf): ModSecurity 3.0.0 and later multipart parser ignores RFC 2231 filename and lets a request with filename="safe.jpg" plus filename=UTF-8''shell.php pass CRS checks, while Go, Python (Flask, FastAPI), Node.js and Java Spring backends may save shell.php. No patch is listed. CVE-2026-73857 (GHSA-jx3r-phvx-2jmj, CWE-787/CWE-824): uninitialised pointer use allowing a fixed write to an attacker-chosen address, affecting 3.0.15, 3.0.16 and v3 master only when SecParseXmlIntoArgs is On or OnlyArgs (default Off). Advisory lists 3.0.17 as fixed but text says a fix is not yet available; verify the release before upgrading. Set SecParseXmlIntoArgs Off now and do not rely on the WAF for upload validation.
For security analysts · Written by AI from 1 source · Wrong?
What to do
- Check that SecParseXmlIntoArgs is set to Off, the workaround given in the advisory for CVE-2026-73857.
- Upgrade ModSecurity once you have confirmed on the official project page that the fixed release is available.
- Do not rely on the WAF alone to judge uploads; have applications ignore the client-supplied filename and generate their own safe name.
- Block script extensions such as .php and store uploads outside the web root, as general good practice not stated in the advisory.
Written by AI from the sources, checked against them
Vulnerabilities
- CVE-2026-104269CVSS 8.6ModSecurity 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 Conten
- CVE-2026-73857CVSS 7.5ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. From 3.0.15 until 3.0.17, XML request body processing with SecParseXmlIntoArgs set to On or OnlyArgs can leave XMLNodes::parsing_ctx_arg uninitialized in the SAX end-element callback. A sin
Full story timeline · 3 updates
Who reported · 1 outlet
Who and what is in it
Products