Skip to content
VulniPulse
UnratedApache Software Foundation Updated

Advisory [CVE-2026-82432] Apache Storm: Description Nimbus validated `topology.blobstore.map` against the calling subject at submission time only

This security Apache Software Foundation advisory covers CVE-2026-82432 affecting Apache Storm.

CVE-2026-82432 Published Sep 14, 2026Updated by vendor Sep 14, 2026
Related products & platforms
Apache Software FoundationUnclassified
Open vendor advisory

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.

Matching phone alertsOptional email delivery

Summary

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 entry naming a

blob whose ACL does not grant them access. Supervisors localise whatever key the map names, placing the

blob's contents into the topology's working directory.

The same advisory covers `listBlobs`, which performed no authorization check and passed no subject, unlike the neighbouring `getBlobMeta` and `beginBlobDownload` operations.

It therefore returned every key in the blobstore to any caller able to reach the Nimbus Thrift port, which provides the key names that make the

above practical. On its own the disclosure is metadata only.

Affected product named by the advisory: Apache Storm.

Affected versions
  • Apache Storm Nimbus 3.0.0 before 3.1.0

Official advisory · medium-confidence parse· fetched 3 hours ago·verify at source

Fixed versions
  • 3.1.0

Official advisory · medium-confidence parse· fetched 3 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Mitigation Upgrade to 3.1.0, where rebalance configuration overrides are validated exactly as submission-time configuration is, against the rebalancing caller, and where `listBlobs` applies the configured authorization.
Temporary workarounds
  • Users who cannot upgrade immediately should restrict rebalance rights to trusted principals, keeping in mind that membership of a topology's `topology.users` or `topology.groups` confers them.

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.