CVE-2026-82432
CVE-2026-82432 — Apache Storm Nimbus: Blobstore Authorization Bypass via Rebalance Configuration Overrides
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 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. 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. 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. Credit The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.
Published Updated Sources: NVD, Apache Software Foundation (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
Unscored
no source published a base score
Remediation
The vendor's own words where we have them.
Upgrade Apache Storm Nimbus to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| Apache | Apache Storm Nimbus | 3.0.0 to < 3.1.0 | Vulnerable |
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-863 · Incorrect Authorization
- Read Application Data
- Read Files or Directories
- Modify Application Data
- Modify Files or Directories
Mitigation: Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Weakness & attack patterns
- CWE-863Incorrect Authorization
Inferred from the weakness class — not observed against this CVE.
Social mentions
Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Initial · CVE published
Sep 14, 2026 · NVD
Added · GHSA-hw7r-wm97-cf8j published (unknown)
Sep 14, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 14, 2026 · SOCRadar CTI
Source activity
Readings a source repeats on a schedule, counted rather than listed.
- 1×Tweets · 1 time tweeted.Sep 14, 2026 · SOCRadar CTI
- 1×CVE appeared in the Cve Trends.Sep 14, 2026 · SOCRadar CTI
- 1×SVRS is calculatedSep 14, 2026 · SOCRadar CTI
References
4 on the record
- lists.apache.org/thread/psy1gj77jhf9y3lhph9yz4f5fovmkz7b
Vendor Advisory
- www.openwall.com/lists/oss-security/2026/09/13/12
Vendor Advisory
- nvd.nist.gov/vuln/detail/CVE-2026-82432
NVD
- github.com/advisories/GHSA-hw7r-wm97-cf8j
Exploit, Third Party Advisory
Coverage
2 stories from the feeds we poll
Elsewhere on this site
- Apacheevery CVE for this vendor
- Access Controlsame class
- CWE-863other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-82432 is Apache Storm Nimbus: Blobstore Authorization Bypass via Rebalance Configuration Overrides, a unscored vulnerability affecting Apache Storm Nimbus from Apache Software Foundation. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-82432. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-82432. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS null describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.
