Skip to main content
cve.nowby Sazabi
Menu
CVEs

CVE

Apache Storm: Supervisor page discloses worker placement of other users' topologies

CVE-2026-94125EUVD-2026-123408GHSA-QJXP-P86M-P4WV

Exploited
No known exploitation
Fix
Fixed in 3.2.0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 3.2.0.

Published
Last modified
Reference
Last checked
11/100 · provisional
Low (apache)
None on Exploit-DB, Metasploit or GitHub

Summary

Apache Storm, a distributed stream processing system, has a flaw in which the Supervisor page exposes the worker placement of other users' topologies, including host, port, owner, and resource assignment, to any authenticated user who can reach Nimbus. An attacker with that access can learn where other users' topology workers are running, and the issue is fixed in a newer release.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

Nimbus returns the worker placement of every topology running on a supervisor, including the host, port, owner and resource assignment of topologies the caller is not authorized to read. In a multi-tenant cluster, an authenticated user who is allowed to access Nimbus can learn where the workers of other users' topologies run. Users are recommended to upgrade to version 3.2.0, which fixes the issue.

cve.now Index

11Pcve.now Index 11 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach10/20Affects Maven packages
  • Severity1/10Rated low by apache
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 33 if advisories confirm default setups are exposed

How the score works · Rankings

Impact

  • Widely used

    9 packages depend on org.apache.storm:storm-server.Source: deps.dev

What to do

  • Upgrade to a fixed version: 3.2.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-94125 (Apache Storm: Supervisor page discloses worker placement of other users' topologies), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-94125 (entry last updated 2026-11-11):
Affected:
- Maven package org.apache.storm:storm-server: from 2.0.0, fixed in 3.2.0
Fixed versions: 3.2.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-94125 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-94125 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Maven): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://lists.apache.org/thread/8of7kv48thj82bb8vqrz6wbglmyldyvv
- http://www.openwall.com/lists/oss-security/2026/11/11/3
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-94125
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-94125"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Record last updated

Affected versions

  • From 2.0.0 · fixed in 3.2.0

    No fix released. The advisory names 3.2.0 as the fix, which the registry doesn't have yet. The latest release, 3.1.0, is still affected.

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Write-ups · 1

Establishes: Technical detail and context.

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-94125

Is CVE-2026-94125 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-94125?

org.apache.storm:storm-server (Maven): from 2.0.0 before 3.2.0.Source: cve.now feed data

How do I fix CVE-2026-94125?

Upgrade to a fixed version: 3.2.0.Source: cve.now feed data

Sources

More CVEs

Related