Skip to main content
CVE-2026-104269VulnerabilityPublished

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

Affects modsecuritySource GCVE Database

0
Compare
Authoritative record:CVE-2026-104269· High 8.6

Not known to be exploited · CVSS 8.6 High : upgrade to 3.0.17 soon.

Data as of 17 Nov 2026, 16:33 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.6
Patch
Available – fixed in 3.0.17
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade modsecurity to 3.0.17.

Affected software

ProductAffectedFixed in
Bitnamimodsecuritypkg:bitnami/modsecurityOther threatsAffected
  • >=3.0.0 <3.0.17
Fixed in
  • 3.0.17

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade ModSecurity to version 3.0.17 or later, where this issue is fixed. Since a patch is available and the fixed version is explicitly stated, applying this official fix is the recommended mitigation.

Description

ModSecurity versions from 3.0.0 up to but not including 3.0.17 have a vulnerability in their multipart parser where the RFC 2231 filename* parameter precedence is not enforced as it is in common backend parsers like Go, Python, Node.js, and Java. This discrepancy allows an attacker to supply a benign filename parameter for ModSecurity and a different encoded filename* that the backend uses, potentially bypassing WAF filename inspection rules. The issue is fixed in version 3.0.17.

References

Community reviews

Loading reviews…