CVE-2021-31412: Possible route enumeration in production mode via RouteNotFoundError view in Vaadin 10, 11-14, and 15-19
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 71.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: com.vaadin:vaadin-bom (Maven) 10.0.19, 14.6.2, 19.0.9.
Low priority for now. Upgrade to com.vaadin:vaadin-bom (Maven) 10.0.19, 14.6.2, 19.0.9 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 24, 2021
- Updated
- Jun 16, 2026
- EPSS
- 1.3% · 71th percentile
- CWE
- CWE-1295
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
CNA vs NVD score
- NVD
- 5.3
- CNA · Vaadin
- 5.3
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Vaadin). Independent of NVD's CPE analysis and usually ahead of it.
Vaadin flow-server
- 1.0.0 and later · before unspecifiedaffected
- unspecified and later · up to and including 1.0.14affected
- 1.1.0 and later · before unspecifiedaffected
- unspecified and later · before 2.0.0affected
- 2.0.0 and later · before unspecifiedaffected
- unspecified and later · up to and including 2.6.1affected
- 3.0.0 and later · before unspecifiedaffected
- unspecified and later · up to and including 6.0.9affected
Vaadin Vaadin
- 10.0.0 and later · before unspecifiedaffected
- unspecified and later · up to and including 10.0.18affected
- 11.0.0 and later · before unspecifiedaffected
- unspecified and later · before 14.0.0affected
- 14.0.0 and later · before unspecifiedaffected
- unspecified and later · up to and including 14.6.1affected
- 15.0.0 and later · before unspecifiedaffected
- unspecified and later · up to and including 19.0.8affected
Affected versions · NVD (10)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- vaadin flow1.0.0 and later · up to 1.0.14 inclusive
- vaadin flow1.1.0 and later · up to 1.4.0 inclusive
- vaadin flow2.0.0 and later · up to 2.6.1 inclusive
- vaadin flow3.0.0 and later · up to 5.0.0 inclusive
- vaadin flow6.0.0 and later · up to 6.0.9 inclusive
- vaadin vaadin10.0.0 and later · up to 10.0.18 inclusive
- vaadin vaadin11.0.0 and later · up to 13.0.0 inclusive
- vaadin vaadin14.0.0 and later · up to 14.6.1 inclusive
- vaadin vaadin15.0.0 and later · up to 18.0.0 inclusive
- vaadin vaadin19.0.0 and later · up to 19.0.8 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | com.vaadin:vaadin-bom | from 10.0.0 · before 10.0.19 | 10.0.19 |
| Maven | com.vaadin:vaadin-bom | from 11.0.0 · before 14.6.2 | 14.6.2 |
| Maven | com.vaadin:vaadin-bom | from 15.0.0 · before 19.0.9 | 19.0.9 |
Same product
vaadin: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-31411Insecure temporary directory usage in frontend build functionality of Vaadin 14 and 15-1931Monitor
- CVE-2021-31407Server classes and resources exposure in OSGi applications using Vaadin 12-14 and 1931Monitor
- CVE-2021-31405Regular expression denial of service (ReDoS) in EmailField component in Vaadin 14 and 15-1730Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-31406Apr 23, 2021 · Timing side channel vulnerability in endpoint request handler in Vaadin 15-1910Monitor
- ← EarlierCVE-2021-31408Apr 23, 2021 · Server session is not invalidated when logout() helper method of Authentication module is used in Vaadin 18-1928Monitor
- Later →CVE-2026-7860May 19, 2026 · Possible information disclosure of environment variables in Vaadin Build Plugins via Failed Frontend Build6Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:com.vaadin:vaadin-bom | 10.0.19 | Package registry (OSV) |
| Maven:com.vaadin:vaadin-bom | 14.6.2 | Package registry (OSV) |
| Maven:com.vaadin:vaadin-bom | 19.0.9 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-1295 · Debug Messages Revealing Unnecessary InformationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.