NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

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

MEDIUM

GHSA-fr26-qjc8-mvjx is a medium-severity (CVSS 5.3) vulnerability in com.vaadin:flow-server. A fix is available for com.vaadin:flow-server — see the affected versions and patch details below.

Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected
☕com.vaadin:flow-server☕com.vaadin:flow-server☕com.vaadin:flow-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.vaadin:flow-server≥ 1.0.0&&< 1.0.151.0.15com.vaadin:flow-server:1.0.15
☕Mavencom.vaadin:flow-server≥ 1.1.0&&< 2.6.22.6.2com.vaadin:flow-server:2.6.2
☕Mavencom.vaadin:flow-server≥ 3.0.0&&< 6.0.106.0.10com.vaadin:flow-server:6.0.10

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.vaadin:flow-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update com.vaadin:flow-server to 1.0.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fr26-qjc8-mvjx is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-fr26-qjc8-mvjx in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Possible route enumeration in production mode via…