# Coraza: Multipart filename\* (RFC 5987) charset restriction lets a decoy filename bypass FILES-based rules Advisory record · `GHSA-3wr7-993q-jrff` - **Identifiers:** `GHSA-3wr7-993q-jrff` · `CVE-2026-114101` · `GO-2026-6691` - **State:** Confirmed - **Severity:** CVSS 6.3 Medium - **Critical:** No - **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-436](https://cwe.mitre.org/data/definitions/436.html) - **Tags:** [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md) · [CWE-436](https://agentprime.io/advisories/tag/cwe-436.md) - **Published:** 8 Oct 2026 - **Updated:** 21 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 8 Oct 2026, 17:51 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/corazawaf/coraza/v3` (Go): affected `<3.8.1`; fixed in `3.8.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Coraza (github.com/corazawaf/coraza/v3) versions before 3.8.1 extract multipart upload filenames with Go's mime.ParseMediaType, which ignores RFC 5987 filename\* values declared with any charset other than utf-8 or us-ascii. A remote attacker can send an upload whose real filename is hidden in such a filename\* value, so FILES-based rules see a harmless name while the backend may use a dangerous one, with no authentication or user interaction needed. Upgrade to version 3.8.1 or later, which decodes filename\* independently of that charset restriction. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 6.3 Medium, CVSS 4.0: `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`, from CNA (VulnCheck) - **CISA KEV:** Not listed. - **EPSS:** 0.0025, the 16th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:11 UTC: First seen by agentprime - 31 Oct 2026, 14:11 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-3wr7-993q-jrff) ## Sources - [GitHub Advisory Database: GHSA-3wr7-993q-jrff](https://github.com/advisories/GHSA-3wr7-993q-jrff) - [OSV: GHSA-3wr7-993q-jrff](https://osv.dev/vulnerability/GHSA-3wr7-993q-jrff) - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .