Skip to main content
CVE-2026-94125VulnerabilityPublished

Nimbus returns the worker placement of every topology running on a supervisor, including the host, port, owner and

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-94125· Medium

Not known to be exploited : upgrade to 3.2.0 when convenient.

Data as of 11 Nov 2026, 16:33 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in 3.2.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Upgrade Apache Storm and org.apache.storm/storm-server to 3.2.0.

Affected software

ProductAffectedFixed in
Apache Stormorg.apache.storm:storm-serverAffected
  • >=2.0.0 <3.2.0
Fixed in
  • 3.2.0
Mavenorg.apache.storm/storm-serverpkg:maven/org.apache.storm/storm-serverOther threatsAffected
  • >=2.0.0 <3.2.0
Fixed in
  • 3.2.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users are recommended to upgrade to Nimbus version 3.2.0, which fixes this information disclosure vulnerability. No other mitigation steps are indicated.

Description

A vulnerability in Nimbus allows an authenticated user with access to Nimbus to retrieve worker placement details of all topologies running on a supervisor, including sensitive information such as host, port, owner, and resource assignments, even for topologies they are not authorized to view. This issue affects multi-tenant clusters where users can learn about other users' topology deployments. The issue is fixed in version 3.2.0.

References

Community reviews

Loading reviews…