CVE-2026-82433: Apache Storm Nimbus, Apache Storm UI: Disclosure of Unredacted Daemon Configuration via Nimbus and the UI
Apache Storm Nimbus and UI return unredacted daemon configuration, including ZooKeeper and keystore secrets, to authorized users.
CVE-2026-82433 (rated moderate) affects Apache Storm Nimbus (storm-server) and Storm UI (storm-webapp) versions 3.0.0 before 3.1.0. The getNimbusConf operation returned the complete daemon configuration without redaction after only a user-level authorization check. Where configured, the response includes storm.zookeeper.auth.payload plus keystore and related secrets.
- getNimbusConf returned full daemon config without redaction
- Only user-level authorization check applied
- Leaks storm.zookeeper.auth.payload and keystore secrets when configured
- Affects storm-server and storm-webapp 3.0.0 before 3.1.0
Vulnerabilities mentionedAll →
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2026-82433 | Unredacted Configuration & Credential Disclosure in Apache Storm Nimbus and UI Apache Storm before 3.1.0 leaks its full daemon configuration, including the ZooKeeper authentication payload (storm.zookeeper.auth.payload) and the TLS keystore/truststore passwords for Thrift, Netty, and ZooKeeper, through two paths: the Nimbus getNimbusConf call, which returns credentials unredacted after only a user-level authorization check, and the UI REST endpoint /api/v1/cluster/configuration, which applied no per-user check at all because it lacked an @AuthNimbusOp annotation and the filter treated a missing annotation as requiring no gate, proxying the request under the UI daemon's own principal. Any user who can pass the UI's ui.filter authentication can trigger the UI path and retrieve secrets that Nimbus itself would have refused to share. An attacker gains Kerberos/TLS credentials and ZooKeeper auth material that could allow impersonating cluster components and further compromise of the Storm cluster and its ZooKeeper ensemble. All Apache Storm deployments prior to 3.1.0 are affected where those credentials are configured. No public proof of concept exists and no exploitation in the wild is known. Do: Upgrade to Apache Storm 3.1.0, which masks credential-bearing configuration values and requires explicit authorization declarations on every UI API endpoint. If you cannot upgrade immediately, place the Storm UI behind an authenticating reverse proxy that restricts /api/v1/cluster/configuration, and review UI access logs for requests to that endpoint. Rotate the ZooKeeper authentication payload and any Thrift, Netty, or ZooKeeper TLS keystore/truststore passwords that were reachable through the exposed endpoints. | 6.5 | — |
| moderatelikely on the order of a few thousand enterprise Storm clusters worldwide, with only a subset (likely hundreds) internet-exposed |
Posted by Richard Zowalla on Sep 13 Severity: moderate Affected versions: - Apache Storm Nimbus (org.apache.storm:storm-server) 3.0.0 before 3.1.0 - Apache Storm UI (org.apache.storm:storm-webapp) 3.0.0 before 3.1.0 Description: Description `getNimbusConf` returned the complete daemon configuration without redaction after only a user-level authorization check. Where the cluster is configured with them, that response includes `storm.zookeeper.auth.payload` and the keystore and...
This source does not provide full text. Read it at seclists.org.