Multipart filename* charset handling bypasses Coraza FILES rules
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Attack requirements
- Present
- Impact type
- —
- Confidentiality · integrity · availability
- None · Low · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA.
Summary
Coraza before 3.8.1 extracts multipart upload filenames with Go's mime.ParseMediaType, which silently ignores RFC 5987 filename* parameters whose charset is not utf-8 or us-ascii. An unauthenticated remote attacker can send a decoy filename or a filename* parameter alone, so FILES-based rules never see the real name and dangerous uploads can reach backends that honor filename*. This is classified as CWE-20, improper input validation.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
Description from the CNA
Coraza before 3.8.1 extracts multipart upload filenames with Go's mime.ParseMediaType, which silently ignores RFC 5987 filename* parameters whose charset is not utf-8 or us-ascii. Unauthenticated attackers can send a decoy filename with filename*=iso-8859-1''shell.php, or filename* alone, so FILES-based rules never see the real name, letting dangerous uploads reach backends that honor filename*.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade Coraza to version 3.8.1 or later, which fixes this issue. CISA's SSVC data indicates a proof of concept exists.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
- Fix · CNA coraza (corazawaf) Fixed in 3.8.1
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
corazawaf coraza 3.8.1
3 records Highest priority Priority MEDIUM 2 MEDIUM, 1 LOW
Other records, highest priority first
- TI-2026-78712 Coraza JSON key collision lets SQL injection evade WAF rulesPriority MEDIUM 64
- TI-2026-78713 Request body inspection bypass in Coraza via Content-Type parametersPriority LOW 36
Timeline
- 2026-10-21 Threatist record created from CVE-2026-114101
- 2026-10-22 Priority changed: MEDIUM → LOW
- 2026-10-28 CISA SSVC decision points changed
- 2026-10-28 Priority changed: LOW → MEDIUM
References
More corazawaf vulnerabilities
- TI-2026-69592 Uncontrolled recursion in Coraza WAF JSON parsing crashes the process CVSS 3.1HIGH 7.5
- TI-2026-71270 Coraza WAF silently drops arguments at ArgumentLimit, enabling rule bypass CVSS 3.1HIGH 7.2
- TI-2026-71268 Off-by-one error in OWASP Coraza jsDecode enables WAF rule bypass CVSS 3.1MEDIUM 5.8
- TI-2026-78712 Coraza JSON key collision lets SQL injection evade WAF rules CVSS 4.0MEDIUM 6.9
- TI-2026-69596 Uncontrolled recursion in Coraza WAF JSON processing exhausts CPU CVSS 3.1MEDIUM 5.9
- TI-2026-71308 CRLF injection in OWASP Coraza WAF native audit log lets attackers forge lines CVSS 3.1MEDIUM 5.8
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences