Possible route enumeration in production mode via RouteNotFoundError view in Vaadin 10, 11-14, and 15-19

published 2021-06-24 5 y ago modified 2026-06-17 4 mo ago also GHSA-qrg9-f472-qwfm , EUVD-2021-1386

cvss: 5.3; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 1.3%; EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits: 0; none known

Improper sanitization of path in default RouteNotFoundError view in com.vaadin:flow-server versions 1.0.0 through 1.0.14 (Vaadin 10.0.0 through 10.0.18), 1.1.0 prior to 2.0.0 (Vaadin 11 prior to 14), 2.0.0 through 2.6.1 (Vaadin 14.0.0 through 14.6.1), and 3.0.0 through 6.0.9 (Vaadin 15.0.0 through 19.0.8) allows network attacker to enumerate all available routes via crafted HTTP request when application is running in production mode and no custom handler for NotFoundException is provided.

Patch / fix

fixed in 3 links 1

maven com.vaadin:vaadin-bom 10.0.19, 14.6.2, 19.0.9
Vaadin Vaadin 14.0.0
Vaadin flow-server 2.0.0

github.com/vaadin/flow#11107 pull request

Exploit prediction

1.32% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
maven	com.vaadin:vaadin-bom	>=10.0.0, <10.0.19 >=11.0.0, <14.6.2 >=15.0.0, <19.0.9	10.0.19 14.6.2 19.0.9

Affected products

Vaadin Vaadin
Vaadin flow-server

Classification

Weakness

CWE-1295 Debug Messages Revealing Unnecessary Information
CWE-20 Improper Input Validation
CWE-668 Exposure of Resource to Wrong Sphere

References

github.com /vaadin/flow/pull/11107
web, patch, third-party-advisory
vaadin.com /security/cve-2021-31412
web, vendor-advisory
github.com /vaadin/platform/security/advisories/GHSA-qrg9-f472-qwfm
web
nvd.nist.gov /vuln/detail/CVE-2021-31412
advisory

Sources

Fencer Vulns 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.

Summary