Skip to content
VulniPulse
Critical10.0Apache Software Foundation Updated

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 affecting Apache Storm.

CVE-2026-82434 Published Sep 14, 2026Updated by vendor Sep 14, 2026
Related products & platforms
Apache Software FoundationBig Data
Open vendor advisory

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.

Matching phone alertsOptional email delivery

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.

Affected versions
  • 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 3 hours ago·verify at source

Fixed versions
  • 3.1.0

Official advisory · high-confidence parse· fetched 3 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • 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.
Temporary workarounds
  • 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 3 hours 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.