CVE-2026-114101 json
Coraza before 3.8.1 Multipart filename* Charset Handling FILES Rule Bypass
published last mo. modified 12d ago also EUVD-2026-106904 , GHSA-3wr7-993q-jrff , GO-2026-6691
- cvss
- 4.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 16%
- public exploits
- 0
- none known
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. 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*.
Patch / fix
- go github.com/corazawaf/coraza/v3 3.8.1
- corazawaf coraza 3.8.1
Is CVE-2026-114101 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 12d ago
Exploit prediction
0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/corazawaf/coraza/security/advisories/GHSA-3wr7-993q-jrff referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.3 | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N |
| CNA | 3.1 | 4.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N |
| GitHub | 3.1 | 4.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N |
| CNA | 4.0 | 6.3 | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/corazawaf/coraza/v3 | <3.8.1 |
3.8.1 |
| go | github.com/corazawaf/coraza | all versions |
no fix listed |
| go | github.com/corazawaf/coraza/v2 | all versions |
no fix listed |
Affected products
- corazawaf coraza
Classification
References
-
github.com
/corazawaf/coraza/commit/5427c501b2fea6ae1305903efef01b3049224a58
web, patch
-
github.com
/corazawaf/coraza/commit/b2a9264437116bdd98a86fe345b2aec1152d3d7c
web, patch
-
github.com
/corazawaf/coraza/commit/cae3c7407e7b84372c207033de03f15f89bf351a
web, patch
-
github.com
/corazawaf/coraza/security/advisories/GHSA-3wr7-993q-jrff
vendor-advisory, exploit, web, advisory
-
vulncheck.com
/advisories/coraza-before-3.8.1-multipart-filename-charset-handling-files-rule-bypass
third-party-advisory
-
github.com
/corazawaf/coraza
package
-
github.com
/corazawaf/coraza/releases/tag/v3.8.1
web
Sources
- CVE List CVE-2026-114101
- GitHub Advisory GHSA-3wr7-993q-jrff
- NVD CVE-2026-114101
- OSV GO-2026-6691
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.