Advisory [CVE-2026-82433] Apache Storm: Description `getNimbusConf` returned the complete daemon configuration without redaction after only a user-level authorization check
This security Apache Software Foundation advisory covers CVE-2026-82433 affecting Apache Storm.
Android app · Google Play
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
`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 truststore passwords for the Thrift, Netty
ZooKeeper TLS configuration. The project masks passwords elsewhere before display, so the omission here is
inconsistent rather than intended.
The UI endpoint `/api/v1/cluster/configuration` compounded this. It carried no `@AuthNimbusOp` annotation,
and the authorization filter treated a missing annotation as "no gate required" and returned immediately, so the endpoint applied no per-user check at all and proxied the request under the UI daemon's own principal.
Any user able to pass `ui.filter` therefore received the full configuration, including principals that Nimbus itself would have refused.
Affected product named by the advisory: Apache Storm.
- Apache Storm Nimbus 3.0.0 before 3.1.0
- Apache Storm UI 3.0.0 before 3.1.0
Official advisory · medium-confidence parse· fetched 3 hours ago·verify at source
- 3.1.0
Official advisory · medium-confidence parse· fetched 3 hours ago·verify at source
Mitigation checklist
- Mitigation Upgrade to 3.1.0, where credential-bearing values are masked before the configuration is served and where every UI API endpoint must declare its authorization explicitly.
- Users who cannot upgrade immediately should place the UI behind an authenticating reverse proxy that restricts `/api/v1/cluster/configuration`, and should rotate the ZooKeeper authentication payload and any TLS keystore or truststore passwords that were reachable through it.
Official advisory · medium-confidence parse· fetched 3 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.