# CVE-2026-84179: Apache Storm Nimbus, Apache Storm UI: Disclosure of Unredacted Merged Daemon Configuration via the Topology Page

> Attackers with topology read access can view unredacted daemon credentials, including ZooKeeper auth and TLS passwords, via the Storm UI topology page.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-gp9q-jh3g-h72p

## What is CVE-2026-84179?

CVE-2026-84179 is a medium-severity vulnerability in Apache Storm Nimbus, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Description

  getTopologyPageInfo merged the Nimbus daemon configuration with the topology's own configuration and returned the result without redaction in the topology_conf field of TopologyPageInfo. The Storm UI copied that value verbatim into the configuration field of GET /api/v1/topology/{id} and of the corresponding metrics endpoint.

  Where the cluster is configured with them, the merged map includes storm.zookeeper.auth.payload, which Storm's own documentation directs operators to keep in storm-cluster-auth.yaml under permissions that deny access from workers, together with the keystore and truststore passwords for the Thrift, Netty and ZooKeeper TLS configuration, and any plugin key whose name denotes a secret.

  getTopologyPageInfo is a topology read-only operation. Under SimpleACLAuthorizer a principal listed in topology.readonly.users or topology.readonly.groups could therefore read daemon credentials that the dedicated cluster configuration API, getNimbusConf, redacts and that is gated on nimbus.users instead. The sibling operations that exist to serve configuration were masked; the topology page, which merges in strictly more daemon state, was not.

  Mitigation

  Upgrade to 3.1.0, where credential-bearing values are masked before any configuration is served over the Nimbus API.

  Users who cannot upgrade immediately should remove any principal that is not trusted with cluster credentials from topology.readonly.users, topology.readonly.groups, topology.users and topology.groups, and should rotate the ZooKeeper authentication payload and any TLS keystore or truststore passwords that were reachable through the topology page.

  Credit
Wanxin Yin (yaklang.io) reported this issue to the Apache Security Team.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-84179?


## How do I fix CVE-2026-84179?

No fix has been published for CVE-2026-84179 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-84179 being exploited?

There is no known exploitation of CVE-2026-84179 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84179 and fix it if it is affected.

What it is: CVE-2026-84179 is a medium-severity vulnerability in Apache Storm Nimbus, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84179 in the wild and no public exploit code.

Affected product: Apache Storm Nimbus. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84179/ (Markdown: https://insights.sbomify.com/CVE-2026-84179/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84179
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84179
- OSV: https://osv.dev/vulnerability/CVE-2026-84179

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84179/
Summaries are generated and may contain mistakes; the official description above is the record.