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

Vaadin vulnerable to possible information disclosure in non visible componentsGHSA-5f9v-mv5g-jh5q

MEDIUMFix: vaadin/flow#15885

GHSA-5f9v-mv5g-jh5q is a medium-severity (CVSS 5.7) Information Exposure vulnerability in com.vaadin:vaadin. A fix is available for com.vaadin:vaadin — see the affected versions and patch details below.

Also known asCVE-2023-25499
Published
Updated
Affected
11 pkgs
Patched
11 / 11
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-5f9v-mv5g-jh5q.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk
0.00%0.36%0.72%1.08%0.2%0.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

11 pkgs affected
☕com.vaadin:vaadin☕com.vaadin:vaadin☕com.vaadin:vaadin☕com.vaadin:vaadin☕com.vaadin:vaadin☕com.vaadin:flow-server☕com.vaadin:flow-server☕com.vaadin:flow-server+3 more

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

Description

When adding non-visible components to the UI in server side, content is sent to the browser in Vaadin 10.0.0 through 10.0.22, 11.0.0 through 14.10.0, 15.0.0 through 22.0.28, 23.0.0 through 23.3.12, 24.0.0 through 24.0.5 and 24.1.0.alpha1 to 24.1.0.beta1, resulting in potential information disclosure.

Affected Packages

11 total 11 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.vaadin:vaadin≥ 10.0.0&&< 10.0.2310.0.23com.vaadin:vaadin:10.0.23
☕Mavencom.vaadin:vaadin≥ 11.0.0&&< 14.10.114.10.1com.vaadin:vaadin:14.10.1
☕Mavencom.vaadin:vaadin≥ 23.0.0&&< 23.3.1323.3.13com.vaadin:vaadin:23.3.13
☕Mavencom.vaadin:vaadin≥ 24.0.0&&< 24.0.624.0.6com.vaadin:vaadin:24.0.6
☕Mavencom.vaadin:vaadin≥ 24.1.0.alpha1&&< 24.1.024.1.0com.vaadin:vaadin:24.1.0
☕Mavencom.vaadin:flow-server≥ 1.0.0&&< 1.0.201.0.20com.vaadin:flow-server:1.0.20

Affected Products

1 product · 12 configurations
Application
vaadinvaadin
≥ 24.0.0 && ≤ 22.0.28
1 version
24.1.0

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:vaadin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update com.vaadin:vaadin to 10.0.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5f9v-mv5g-jh5q is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### Description When adding non-visible components to the UI in server side, content is sent to the browser in Vaadin 10.0.0 through 10.0.22, 11.0.0 through 14.10.0, 15.0.0 through 22.0.28, 23.0.0 through 23.3.12, 24.0.0 through 24.0.5 and 24.1.0.alpha1 to 24.1.0.beta1, resulting in potential information disclosure. * https://vaadin.com/security/cve-2023-25499
O3 Security · Impact-Aware SCA

Is GHSA-5f9v-mv5g-jh5q in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Vaadin vulnerable to possible information disclosure in…