BIT-modsecurity2-2026-104269

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/modsecurity2/BIT-modsecurity2-2026-104269.json
JSON Data
https://api.osv.dev/v1/vulns/BIT-modsecurity2-2026-104269
Aliases
Published
2026-11-17T11:52:19Z
Modified
2026-11-17T13:41:15Z
Summary
ModSecurity: RFC 2231 `filename*` Parameter Bypasses Multipart Filename Rules on RFC-Compliant Backends (Go, Python, Node, Java)
Details

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.

Database specific
{
    "cpes":  [
        "cpe:2.3:a:trustwave:modsecurity:*:*:*:*:*:*:*:*"
    ],
    "severity":  "High"
}
References

Affected packages

Bitnami / modsecurity2

Package

Name
modsecurity2
Purl
pkg:bitnami/modsecurity2

Severity

  • 8.6 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
3.0.0
Fixed
3.0.17

Database specific

source
"https://github.com/bitnami/vulndb/tree/main/data/modsecurity2/BIT-modsecurity2-2026-104269.json"