Skip to content
VulniPulse
Advisory severityMedium6.5Apache Software Foundation

Medium [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 medium-severity Apache Software Foundation advisory covers CVE-2026-84179; related products: Apache Security Team.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-84179 Source published Source updated

VulniPulse record published Record updated

CVE-2026-84179
Related products & platforms
Apache Software FoundationBig Data
Open source advisory

Get an email when Apache Software Foundation Data & Analytics (Spark/Hadoop/Gravitino) publishes the next one.

See Apache Software Foundation Data & Analytics (Spark/Hadoop/Gravitino)'s last 90 days of advisories first. Then choose the free weekly digest, or a free month of real-time alerts with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Apache Software Foundation Data & Analytics (Spark/Hadoop/Gravitino)

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 product named by the advisory: Apache Security Team.

Affected versions
  • Apache Storm Nimbus 3.0.0 before 3.1.0
  • Apache Storm UI 3.0.0 before 3.1.0

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions
  • 3.1.0

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • 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 · high-confidence parse· fetched 2 months ago·verify at source

All Apache Software Foundation advisories

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 34 official vendor sources and 160+ reviewed platform categories.

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.