Quick answers
- Is CVE-2026-35565 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-35565 being exploited in the wild.
- How severe is CVE-2026-35565?
- Medium severity, with a CVSS score of 5.4, published 13 April 2026.
- Which products and versions are affected?
- org.apache.storm:storm-webapp (Maven) < 2.8.6, ECOSYSTEM:introduced=0,fixed=2.8.6.
- Is there a fix for CVE-2026-35565?
- Yes. org.apache.storm:storm-webapp (Maven): upgrade to 2.8.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-35565 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-35565?
- Check whether you run Apache Storm or org.apache.storm:storm-webapp (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- org.apache.storm:storm-webapp (Maven): upgrade to 2.8.6 or later
# set org.apache.storm:storm-webapp to 2.8.6 in your pom.xml or build.gradle
Technical details
A stored cross-site scripting (XSS) vulnerability exists in the Apache Storm UI visualization component. The functions parseNode() and parseEdge() in the visualization JavaScript interpolate topology metadata—including component IDs, stream names, and grouping values—directly into the HTML DOM via innerHTML without sanitization. An authenticated attacker with topology submission rights can craft a malicious topology containing JavaScript payloads (e.g., within a bolt ID using an onerror handler). When an administrator views the visualization, the payload is rendered via vis.js tooltips, leading to script execution and potential privilege escalation. The issue is fixed in version 2.8.6.
Affected products
- Apache Storm UI before 2.8.6
Identifiers
- CVE-2026-35565
- GHSA-f2hp-qw27-8wfq
Timeline
- 2026-04-12: patched: Version 2.8.6 released with security fixes.
- 2026-04-13: disclosed: Initial advisory publication.