Read the docs

Vaadin Flow download file name injection lets attackers rename files

Priority LOW 22CWE-116Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
Active
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
None · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Vaadin Flow writes an untrusted download file name into the Content-Disposition header without escaping it, so a double quote in the name ends the quoted filename early. An attacker who can supply the file name, for example through an upload that the application later re-serves, can add a filename* parameter. Browsers prefer filename*, so the file is saved under an attacker chosen name and extension, which bypasses file name or extension restrictions. The flaw is in DownloadEvent.setFileName and inline, and exploitation requires user interaction.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00235 14th percentileScored 2026-11-16
Fix Fixed vaadin (vaadin): 24.9.26, 24.10.14, 25.2.13 +1vaadin-core (vaadin): 24.9.26, 24.10.14, 25.2.13 +1+1 more product

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
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

VendorProductAffected versionsFixed inStatusSource
Vaadinvaadin24.8.0 – 24.8.17; 24.9.0 to before 24.9.26; 24.10.0 to before 24.10.14; 25.0.0 – 25.0.13; 25.1.0 – 25.1.13; 25.2.0 to before 25.2.13; 25.3.0 to before 25.3.524.9.26, 24.10.14, 25.2.13, 25.3.5Patch availableCNA
Vaadinvaadin-core24.8.0 – 24.8.17; 24.9.0 to before 24.9.26; 24.10.0 to before 24.10.14; 25.0.0 – 25.0.13; 25.1.0 – 25.1.13; 25.2.0 to before 25.2.13; 25.3.0 to before 25.3.524.9.26, 24.10.14, 25.2.13, 25.3.5Patch availableCNA
Vaadinflow24.8.0 – 24.8.16; 24.9.0 to before 24.9.31; 24.10.0 to before 24.10.17; 25.0.0 – 25.0.15; 25.1.0 – 25.1.19; 25.2.0 to before 25.2.16; 25.3.0 to before 25.3.624.9.31, 24.10.17, 25.2.16, 25.3.6Patch availableCNA
  • vaadin VendorVaadin Affected 24.8.0 – 24.8.17; 24.9.0 to before 24.9.26; 24.10.0 to before 24.10.14; 25.0.0 – 25.0.13; 25.1.0 – 25.1.13; 25.2.0 to before 25.2.13; 25.3.0 to before 25.3.5 Fixed in 24.9.26, 24.10.14, 25.2.13, 25.3.5 Patch available CNA
  • vaadin-core VendorVaadin Affected 24.8.0 – 24.8.17; 24.9.0 to before 24.9.26; 24.10.0 to before 24.10.14; 25.0.0 – 25.0.13; 25.1.0 – 25.1.13; 25.2.0 to before 25.2.13; 25.3.0 to before 25.3.5 Fixed in 24.9.26, 24.10.14, 25.2.13, 25.3.5 Patch available CNA
  • flow VendorVaadin Affected 24.8.0 – 24.8.16; 24.9.0 to before 24.9.31; 24.10.0 to before 24.10.17; 25.0.0 – 25.0.15; 25.1.0 – 25.1.19; 25.2.0 to before 25.2.16; 25.3.0 to before 25.3.6 Fixed in 24.9.31, 24.10.17, 25.2.16, 25.3.6 Patch available CNA

Remediation

Upgrade the vaadin and vaadin-core packages to 24.9.26, 24.10.14, 25.2.13 or 25.3.5, and the flow package to 24.9.31, 24.10.17, 25.2.16 or 25.3.6. The sources list no fixed version for Vaadin 24.8 and 25.0.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

  • Fix · CNA vaadin (vaadin) Fixed in 24.9.26, 24.10.14, 25.2.13, 25.3.5
  • Fix · CNA vaadin-core (vaadin) Fixed in 24.9.26, 24.10.14, 25.2.13, 25.3.5
  • Fix · CNA flow (vaadin) Fixed in 24.9.31, 24.10.17, 25.2.16, 25.3.6

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-120326
  2. 2026-11-13 CISA SSVC decision points changed

References

  • TI-2026-81073 Vaadin push endpoint reflects any Origin and allows credentials CVSS 4.0LOW 2.3
  • TI-2026-78950 Session lock leak in Vaadin Framework 8 allows denial of service CVSS 4.0HIGH 8.7
  • TI-2021-11539 Server classes and resources exposure in OSGi applications using Vaadin 12-14 and 19 CVSS 3.1HIGH 8.6
  • TI-2021-11542 Project sources exposure in Vaadin Designer CVSS 3.1HIGH 8.6
  • TI-2026-78949 Multiple flaws in Highcharts bundled with Vaadin Charts CVSS 4.0HIGH 8.4
  • TI-2020-18603 Regular expression Denial of Service (ReDoS) in EmailValidator class in Vaadin 7 CVSS 3.1HIGH 7.5
See all 36 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences