PoC Monitor
← All CVEs
CVE-2026-104269published 5 Nov 2026 15:51 UTCData: JSON · API

Owasp-modsecurity ModSecurity

ModSecurity: RFC 2231 `filename*` Parameter Bypasses Multipart Filename Rules on RFC-Compliant Backends (Go, Python, Node, Java)

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS8.6high · scored by CNA · CWE-436
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

owasp-modsecurity ModSecurity
  • >= 3.0.0, < 3.0.17

Fixed in 3.0.17

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published5 Nov 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.