Critical [CVE-2026-82434] Apache Storm: Description When ZooKeeper authentication is configured, Storm deliberately retains `storm.zookeeper.topology.auth.payload` in the topology configuration, because workers need it
This critical-severity Apache Software Foundation advisory covers CVE-2026-82434; related products: Apache Storm.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
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).
Summary
When ZooKeeper authentication is configured, Storm deliberately retains `storm.zookeeper.topology.auth.payload` in the topology configuration, because workers need it.
Nimbus then served that configuration verbatim to any caller holding read-only topology permissions, so a user whose
only grant was the ability to view a topology received its ZooKeeper credential.
That credential is not read-only. The cluster state implementation uses write-capable ACLs for worker
heartbeats, backpressure and error state, so a recipient can forge or remove that state for the topology concerned.
It is not a write credential on assignments.
The same advisory covers the submission client, which logged the generated payload at INFO on every submission that generated one, and the SASL handlers, which logged it at DEBUG.
The credential therefore also reached any log aggregation or support bundle collected from the cluster.
Affected product named by the advisory: Apache Storm.
- Apache Storm Nimbus 3.0.0 before 3.1.0
- Apache Storm Client 3.0.0 before 3.1.0
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
Mitigation checklist
- The cluster state implementation uses write-capable ACLs for worker heartbeats, backpressure and error state, so a recipient can forge or remove that state for the topology concerned.
- Mitigation Upgrade to 3.1.0, where the payload is removed from the configuration served to read-only callers and is no longer written to logs.
- Users who cannot upgrade immediately should rotate `storm.zookeeper.topology.auth.payload` for existing topologies, review retained logs and support bundles for the value, and restrict read-only topology permissions to trusted principals.
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
More Apache Software Foundation advisories
- CVE-2026-82427Sep 14, 2026Apache Storm: Description A topology's `topology.blobstore.map` lets the submitter choose
- CVE-2026-82428Sep 14, 2026Apache Storm: Description Dependency artifacts uploaded with `storm jar --artifacts` were
- CVE-2026-82429Sep 14, 2026Apache Storm: Description The setuid-root `worker-launcher` binary adjusts ownership
- CVE-2026-82430Sep 14, 2026Apache Storm: Description When launching a Docker or OCI worker, the setuid-root
- CVE-2026-82431Sep 14, 2026Apache Storm: Description `SimpleACLAuthorizer` evaluated the user-level command set
- CVE-2026-82433Sep 14, 2026Apache Storm: Description `getNimbusConf` returned the complete daemon configuration
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.