Quick answers
- Is CVE-2026-82433 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82433 being exploited in the wild.
- How severe is CVE-2026-82433?
- Medium severity, with a CVSS score of 6.5, published 14 September 2026.
- Which products and versions are affected?
- Apache Storm before 3.1.0.
- Is there a fix for CVE-2026-82433?
- A patch was published on 2026-09-14: fix released in version 3.1.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82433 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-82433?
- Check whether you run Apache Storm at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability consists of two authorization and disclosure flaws: (1) the `getNimbusConf` RPC method performed only user-level authorization but returned the complete daemon configuration without redacting sensitive values such as `storm.zookeeper.auth.payload` and TLS passwords; (2) the UI endpoint `/api/v1/cluster/configuration` lacked the `@AuthNimbusOp` annotation, causing the authorization filter to treat it as unrestricted and apply no per-user checks, proxying requests under the UI daemon's own principal. This allowed any user who passed the basic UI filter to retrieve the full configuration including credentials that Nimbus would have refused. The vulnerability is network-reachable via the UI and requires only UI-level access to exploit. An attacker can obtain credentials used for ZooKeeper authentication and TLS connections, enabling further compromise of the Storm cluster and its associated infrastructure.
Affected products
- Apache Storm before 3.1.0
Timeline
- 2026-09-14: disclosed
- 2026-09-14: patched: fix released in version 3.1.0