ZeroHour
oss-securitypublished ()ingested

CVE-2026-82432: Apache Storm Nimbus: Blobstore Authorization Bypass via Rebalance Configuration Overrides

mediumVulnerabilityimportance 35CVE-2026-82432
AI summary · glm-5.3

Apache Storm Nimbus blobstore authorization bypass via rebalance configuration overrides, fixed in 3.1.0.

CVE-2026-82432 (rated moderate) affects Apache Storm Nimbus (storm-server) versions 3.0.0 before 3.1.0. Nimbus validates topology.blobstore.map against the calling subject only at topology submission time. The rebalance operation accepts configuration overrides and strips a small set of keys but never re-runs that validation, so a caller authorized only to rebalance a topology can introduce an unauthorized blobstore map.

  • Blobstore map validated only at submission, not during rebalance
  • Rebalance config overrides can inject unauthorized blobstore entries
  • Requires caller already authorized to rebalance the topology
  • Affects storm-server 3.0.0 before 3.1.0

Vulnerabilities mentionedAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2026-82432
Authorization Bypass in Apache Storm Nimbus Blobstore via Rebalance Overrides

Apache Storm's Nimbus daemon validated the `topology.blobstore.map` configuration only at topology submission time, not when configuration overrides were supplied through the rebalance operation, so any caller authorized to rebalance a topology — including members of its `topology.users` or `topology.groups` — could name a blob whose ACL does not grant them access; Supervisors then localize that blob's contents into the topology's working directory, giving the rebalancer an unauthorized read of the blob. The same advisory covers the `listBlobs` Thrift operation, which performed no authorization check and passed no subject, returning every key in the blobstore to any caller able to reach the Nimbus Thrift port — this key-name disclosure (metadata only on its own) is what makes the blobstore read practical. An attacker therefore gains unauthorized access to blob contents, which in Storm deployments can include code, credentials, or other sensitive artifacts. Affected installations are those running Apache Storm Nimbus with authorization configured on versions prior to the 3.1.0 release. No public proof of concept exists and no exploitation has been reported.

Do: Upgrade to Apache Storm 3.1.0, where rebalance configuration overrides are validated against the rebalancing caller exactly as submission-time configuration, and `listBlobs` applies the configured authorization. If immediate upgrade is not possible, restrict rebalance rights to trusted principals — noting that membership in a topology's `topology.users` or `topology.groups` confers them — and limit network access to the Nimbus Thrift port to trusted clients only. Review the blobstore for sensitive blobs and audit past rebalance operations for unexpected `topology.blobstore.map` overrides or unexplained `listBlobs` calls.

8.1
  • Apache Software Foundation Storm (Nimbus daemon blobstore and rebalance operations) all versions prior to 3.1.0; fixed in 3.1.0
moderate≈ low thousands of Storm clusters worldwide, with only a few hundred Nimbus Thrift ports internet-exposed (estimate)
Full article

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 Description: Description Nimbus validated `topology.blobstore.map` against the calling subject at submission time only. The rebalance operation accepts configuration overrides and stripped a small set of keys from them, but never re-ran that validation, so a caller authorised to rebalance a topology could introduce a blobstore map...

This source does not provide full text. Read it at seclists.org.