Advisory [CVE-2026-84179] Apache Security Team: 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
This security Apache Software Foundation advisory covers CVE-2026-84179 affecting Apache Storm Nimbus, Apache Storm UI, Apache Security Team.
Android app · Google Play
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
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.
Affected products named by the advisory: Apache Storm Nimbus; Apache Storm UI; Apache Security Team.
- Apache Storm Nimbus 3.0.0 before 3.1.0
- Apache Storm UI 3.0.0 before 3.1.0
Official advisory · medium-confidence parse· fetched 59 minutes ago·verify at source
- 3.1.0
Official advisory · medium-confidence parse· fetched 59 minutes ago·verify at source
Mitigation checklist
- 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.
Official advisory · medium-confidence parse· fetched 59 minutes ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.