---
id: "CVE-2026-120326"
page: "https://infrastack.ai/live/CVE-2026-120326"
kind: "vulnerability"
aliases: ["CVE-2026-120326"]
title: "Vaadin Flow: download file names let attackers pick saved file extension"
severity: "medium"
cvss: 4.8
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["file-download", "java", "package", "vaadin", "vaadin-flow"]
not_affected_if: ["fixed-version", "no-download-api", "server-generated-file-names"]
published_at: "2026-11-10T12:17:16+00:00"
first_seen_at: "2026-11-10T12:21:53+00:00"
updated_at: "2026-11-10T12:22:49+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-120326", "first_seen_at": "2026-11-10T12:21:53+00:00"}]
exploit_sources: []
---

# Vaadin Flow: download file names let attackers pick saved file extension

Link for people: https://infrastack.ai/live/CVE-2026-120326 (this .md is for agents)

Vaadin Flow's DownloadEvent.setFileName and inline methods do not escape the download file name in the Content-Disposition header. An attacker who controls a file name the application serves can add a filename* parameter, so browsers save the file under a name and extension the attacker chooses.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the Vaadin Flow version in the project build file (pom.xml or build.gradle) for `com.vaadin` dependencies.
- Search the application code for calls to `DownloadEvent.setFileName(` or `inline(` that pass user-supplied file names.
- Versions in the affected ranges: `24.8.0` to `24.8.17`, `24.9.0` to `24.9.25`, `24.10.0` to `24.10.13`, `25.0.0` to `25.0.13`, `25.1.0` to `25.1.13`, `25.2.0` to `25.2.12`, `25.3.0` to `25.3.4`.

## Fix

- Vaadin 24.9: upgrade to `24.9.26`
- Vaadin 24.10: upgrade to `24.10.14`
- Vaadin 25.2: upgrade to `25.2.13`
- Vaadin 25.3: upgrade to `25.3.5`

## Timeline

- 2026-11-10T12:21:53+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-120326

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_