How severe is GHSA-7wwv-79xw-rvvg?

No CVSS score has been assigned to GHSA-7wwv-79xw-rvvg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7wwv-79xw-rvvg?

GHSA-7wwv-79xw-rvvg affects the following packages: com.vaadin:vaadin-server (Maven), com.vaadin:vaadin-server (Maven), com.vaadin:vaadin (Maven), com.vaadin:vaadin (Maven), com.vaadin:vaadin (Maven), com.vaadin:vaadin-spreadsheet-flow (Maven), com.vaadin:vaadin-spreadsheet-flow (Maven), com.vaadin:vaadin-spreadsheet-flow (Maven). Ecosystems affected: Maven.

How do I fix GHSA-7wwv-79xw-rvvg?

Update com.vaadin:vaadin-server to 7.7.50 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7wwv-79xw-rvvg is resolved across your whole dependency graph.

How do I detect GHSA-7wwv-79xw-rvvg in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.vaadin:vaadin-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-7wwv-79xw-rvvg if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-7wwv-79xw-rvvg?

O3 pinpoints whether GHSA-7wwv-79xw-rvvg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-7wwv-79xw-rvvg actively exploited in the wild?

No public exploit code has been indexed for GHSA-7wwv-79xw-rvvg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-7wwv-79xw-rvvg?

GHSA-7wwv-79xw-rvvg is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-7wwv-79xw-rvvg published, and has it been updated?

GHSA-7wwv-79xw-rvvg was published on January 5, 2026 and was last updated on February 3, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

GHSA-7wwv-79xw-rvvg

Fix: vaadin/flow-components#8285

GHSA-7wwv-79xw-rvvg is a Cross-site Scripting (XSS) vulnerability in com.vaadin:vaadin-server. O3 Security confirms whether GHSA-7wwv-79xw-rvvg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Vaadin vulnerable to Cross-site Scripting

Also known asCVE-2025-15022

Published

Jan 5, 2026

Updated

Feb 3, 2026

Affected

8 pkgs

Patched

8 / 8

Exploits

None indexed

Exploitation data as of Feb 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

8 pkgs affected

☕com.vaadin:vaadin-server☕com.vaadin:vaadin-server☕com.vaadin:vaadin☕com.vaadin:vaadin☕com.vaadin:vaadin☕com.vaadin:vaadin-spreadsheet-flow☕com.vaadin:vaadin-spreadsheet-flow☕com.vaadin:vaadin-spreadsheet-flow

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

Action captions in Vaadin accept HTML by default but were not sanitized, potentially allowing Cross-site Scripting (XSS) if caption content is derived from user input.

In Vaadin Framework 7 and 8, the Action class is a general-purpose class that may be used by multiple components. The fixed versions sanitize captions by default and provide an API to explicitly enable HTML content mode for backwards compatibility.

In Vaadin 23 and newer, the Action class is only used by the Spreadsheet component. The fixed versions sanitize HTML using Jsoup with a relaxed safelist.

Vaadin 14 is not affected as Spreadsheet component was not supported.

Users of affected versions should apply the following mitigation or upgrade. Releases that have fixed this issue include:

Product version Vaadin 7.0.0 - 7.7.49 Vaadin 8.0.0 - 8.29.1 Vaadin 23.1.0 - 23.6.5 Vaadin 24.0.0 - 24.8.13 Vaadin 24.9.0 - 24.9.6

Mitigation Upgrade to 7.7.50 Upgrade to 8.30.0 Upgrade to 23.6.6 Upgrade to 24.8.14 or 24.9.7 Upgrade to 25.0.0 or newer

Artifacts Maven coordinatesVulnerable versionsFixed versioncom.vaadin:vaadin-server 7.0.0 - 7.7.49 ≥7.7.50 com.vaadin:vaadin-server 8.0.0 - 8.29.1 ≥8.30.0 com.vaadin:vaadin 23.1.0 - 23.6.5 ≥23.6.6 com.vaadin:vaadin24.0.0 - 24.8.13 ≥24.8.14 com.vaadin:vaadin24.9.0 - 24.9.6 ≥24.9.7 com.vaadin:vaadin-spreadsheet-flow 23.1.0 - 23.6.5 ≥23.6.6 com.vaadin:vaadin-spreadsheet-flow 24.0.0 - 24.8.13 ≥24.8.14 com.vaadin:vaadin-spreadsheet-flow 24.9.0 - 24.9.6 ≥24.9.7

Affected Packages

8 total 8 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.vaadin:vaadin-server`	≥ 7.0.0&&< 7.7.50	7.7.50
☕Maven	`com.vaadin:vaadin-server`	≥ 8.0.0&&< 8.30.0	8.30.0
☕Maven	`com.vaadin:vaadin`	≥ 23.1.0&&< 23.6.6	23.6.6
☕Maven	`com.vaadin:vaadin`	≥ 24.0.0&&< 24.8.14	24.8.14
☕Maven	`com.vaadin:vaadin`	≥ 24.9.0&&< 24.9.7	24.9.7
☕Maven	`com.vaadin:vaadin-spreadsheet-flow`	≥ 23.1.0&&< 23.6.6	23.6.6

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.vaadin:vaadin-server. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.vaadin:vaadin-server to 7.7.50 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7wwv-79xw-rvvg is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-7wwv-79xw-rvvg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-7wwv-79xw-rvvg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Action captions in Vaadin accept HTML by default but were not sanitized, potentially allowing Cross-site Scripting (XSS) if caption content is derived from user input. In Vaadin Framework 7 and 8, the Action class is a general-purpose class that may be used by multiple components. The fixed versions sanitize captions by default and provide an API to explicitly enable HTML content mode for backwards compatibility. In Vaadin 23 and newer, the Action class is only used by the Spreadsheet component. The fixed versions sanitize HTML using Jsoup with a relaxed safelist. Vaadin 14 is not affected

O3 Security · Impact-Aware SCA

Is GHSA-7wwv-79xw-rvvg in your dependencies?

O3 detects GHSA-7wwv-79xw-rvvg across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works