CVE-2026-82434 Details
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 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. Credit The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.
A vulnerability exists in Apache Storm Nimbus and the Storm Client, both in versions 3.0.0 prior to 3.1.0, when ZooKeeper authentication is enabled. Storm retains the 'storm.zookeeper.topology.auth.payload' in the topology configuration for worker use. Nimbus then exposes this configuration to any user with read-only topology permissions, inadvertently disclosing the ZooKeeper credential. This credential is not read-only; it allows manipulation of the cluster state for the associated topology, including forging or removing worker heartbeat states, backpressure, and error states. Additionally, the Storm submission client logs this payload at the INFO level, and SASL handlers log it at DEBUG, potentially exposing the credential through log aggregation or support bundles.
Users should upgrade to Apache Storm version 3.1.0 or later, where this issue is addressed. For those unable to upgrade immediately, it is recommended to rotate the 'storm.zookeeper.topology.auth.payload' for existing topologies, review logs and support bundles for the credential, and restrict read-only topology permissions to trusted principals.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Sep 14, 2026CISA-ADP
Assessed Sep 14, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| http://www.openwall.com/lists/oss-security/2026/09/13/14 | CVE | AdvisoryMailing List |
| http://www.openwall.com/lists/oss-security/2026/09/13/23 | CVE | Mailing ListRemedy |
| https://lists.apache.org/thread/1t7hggrz59rdq792qm1pnkqj0ogm2szq | [email protected] | AdvisoryMailing ListRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-522 | Insufficiently Protected Credentials | [email protected] |
| CWE-532 | Insertion of Sensitive Information into Log File | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| Apache Storm Nimbus | >= 3.0.0, < 3.1.0 (semver) |
CPE
Remediation
| |
| Apache Storm Client | >= 3.0.0, < 3.1.0 (semver) |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 14, 2026 | CVE Modified | CISA-ADP |
| Sep 14, 2026 | New CVE Received | [email protected] |
| Sep 14, 2026 | CVE Modified | CVE |
Volerion