Topology credential disclosure via configuration and logs
Published Sep 14, 2026 · Updated Sep 14, 2026
Credential exposure in Apache Storm Nimbus and Client 3.0.0 allows remote authenticated users to obtain topology ZooKeeper credentials. Nimbus returns the retained authentication payload in topology configuration, while client and SASL handlers write it to logs. Read-only topology access or access to aggregated logs is sufficient; the credential can forge or remove heartbeat, backpressure, and error state.
Summary
What happened
Credential exposure in Apache Storm Nimbus and Client 3.0.0 allows remote authenticated users to obtain topology ZooKeeper credentials. Nimbus returns the retained authentication payload in topology configuration, while client and SASL handlers write it to logs. Read-only topology access or access to aggregated logs is sufficient; the credential can forge or remove heartbeat, backpressure, and error state.
The record
- CVE
- CVE-2026-82434
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Storm Nimbus
- Classifications
- T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.0 <3.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo