# CVE-2026-94125: Apache Storm Nimbus information disclosure in worker placement

Source: https://junglewise.ai/threats/cve-2026-94125-nimbus-returns-the-worker-placement-of-every-topology-running-on  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-11. Updated: 2026-11-11  
License: CC BY 4.0 with a link back

CVE-2026-94125 · Severity: info · Published 2026-11-11

Apache Storm is a distributed real-time data processing platform used for streaming analytics. The Nimbus component, which manages cluster resources, exposes sensitive details about running topologies (including host, port, and owner information) to any authenticated user, even those not authorized to access specific topologies. In a multi-tenant cluster, this allows attackers to map out competing organizations' infrastructure and worker deployment patterns.

Technologies: [Apache Storm](https://junglewise.ai/threats/technologies/storm). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## Quick answers

**Is CVE-2026-94125 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-94125 being exploited in the wild.

**How severe is CVE-2026-94125?** Informational severity, published 11 November 2026.

**Which products and versions are affected?** Apache Storm before 3.2.0.

**Is there a fix for CVE-2026-94125?** Yes: fixed in 3.2.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-94125 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-94125?** Check whether you run Apache Storm 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

- Fixed in 3.2.0

## Technical details

The vulnerability is an information disclosure flaw in Apache Storm Nimbus where the API endpoint returning worker placement details does not properly enforce authorization checks. An authenticated but unprivileged user can query worker locations for topologies owned by other tenants, exposing deployment topology, host addresses, ports, and resource assignments without authorization. The fix is available in version 3.2.0.

## Affected products

- Apache Storm before 3.2.0

## Timeline

- 2026-11-11: disclosed

## References

- [https://repo.maven.apache.org/maven2](https://repo.maven.apache.org/maven2)
- [https://lists.apache.org/thread/8of7kv48thj82bb8vqrz6wbglmyldyvv](https://lists.apache.org/thread/8of7kv48thj82bb8vqrz6wbglmyldyvv)

## Related threats

- [Apache Storm Logviewer symlink traversal in worker logs](https://junglewise.ai/threats/cve-2026-124495-when-workers-run-as-the-topology-owner-the-logviewer-serves)
- [Apache Storm arbitrary class instantiation in scheduler](https://junglewise.ai/threats/cve-2026-82440-description-nimbus-instantiates-the-class-named-by-a-topology-s)
- [Apache Storm unsafe deserialization in state serialization](https://junglewise.ai/threats/cve-2026-82436-description-defaultstateserializer-used-to-persist-and-restore)
- [Apache Storm CORS misconfiguration allows credential-based data exposure](https://junglewise.ai/threats/cve-2026-82438-apache-storm-cors-misconfiguration-allows-credential-based-data)
- [Apache Storm Logviewer access control bypass in daemon logs](https://junglewise.ai/threats/cve-2026-82437-apache-storm-logviewer-access-control-bypass-in-daemon-logs)