CVE-2026-120326Unescaped Download File Name Allows Content-Disposition Parameter Injection in Vaadin Flow
- 4.8MediumCVSS base score
- 0.24%Exploitation in 30 daysEPSS · top 85% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
DownloadEvent.setFileName(String) in Vaadin Flow writes the download file name into the Content-Disposition header without escaping it. When the name is pure US-ASCII the header is built as attachment; filename="<name>" with the name inserted verbatim, so a double quote in the name ends the quoted string early and the rest of the name is read by the browser as further header parameters. The inline(String) variant, present from Vaadin 25.0, builds the name the same way. An application that passes an untrusted file name to either method, for example when re-serving a file under the name it was uploaded with, lets an attacker add a filename* parameter. Browsers prefer filename* over filename, so the file is saved under a name and extension of the attacker's choosing, which defeats any file name or extension restriction the application enforces. The attacker cannot change the attachment or inline disposition itself and cannot split the header. Users of affected versions should apply the following mitigation or upgrade. Releases that have fixed this issue include: Product version Vaadin 24.8.0 - 24.8.17 Vaadin 24.9.0 - 24.9.25 Vaadin 24.10.0 - 24.10.13 Vaadin 25.0.0 - 25.0.13 Vaadin 25.1.0 - 25.1.13 Vaadin 25.2.0 - 25.2.12 Vaadin 25.3.0 - 25.3.4 Mitigation No fixed release on this line, upgrade to 24.9.26 or newer Upgrade to 24.9.26 Upgrade to 24.10.14 No fixed release on this line, upgrade to 25.2.13 or newer No fixed release on this line, upgrade to 25.2.13 or newer Upgrade to 25.2.13 Upgrade to 25.3.5 Vaadin versions below 24.8 are not affected: the DownloadEvent API does not exist in them.
Timeline
ID reserved
By Vaadin
- 9 days later
· 9 days later
Published
- 3 days later
· 3 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| VaadinCNA (assigner) | 4.0 | Medium4.8 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N |
| NVDNVD · Awaiting Analysis | 4.0 | Medium4.8 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/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 |
- EPSS (exploitation in 30 days)
- 0.24% · top 85% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.8.
Affected products
- affected 24.8.0 – ≤ 24.8.17
- affected 24.9.0 – < 24.9.26
- affected 24.10.0 – < 24.10.14
- affected 25.0.0 – ≤ 25.0.13
- affected 25.1.0 – ≤ 25.1.13
- affected 25.2.0 – < 25.2.13
- affected 25.3.0 – < 25.3.5
- affected 24.8.0 – ≤ 24.8.17
- affected 24.9.0 – < 24.9.26
- affected 24.10.0 – < 24.10.14
- affected 25.0.0 – ≤ 25.0.13
- affected 25.1.0 – ≤ 25.1.13
- affected 25.2.0 – < 25.2.13
- affected 25.3.0 – < 25.3.5
- affected 24.8.0 – ≤ 24.8.16
- affected 24.9.0 – < 24.9.31
- affected 24.10.0 – < 24.10.17
- affected 25.0.0 – ≤ 25.0.15
- affected 25.1.0 – ≤ 25.1.19
- affected 25.2.0 – < 25.2.16
- affected 25.3.0 – < 25.3.6
What to do
Solution: Users of affected versions should apply the following mitigation or upgrade.
Workaround: Escape or reject double quotes, backslashes and control characters in any file name that does not come from the application itself before passing it to DownloadEvent.setFileName or DownloadEvent.inline.
References
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-120893 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-120326)Record last updated .