CVE-2026-82434

/// Technical description

Description

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.

Mitigation

Upgrade to 3.1.0, where the payload is removed from the con

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References