CVE-2026-82432Not yet in NVD's feed. The description, CVSS and CWE below come from the CVE Numbering Authority's own record, not from NVD analyst review. NVD's own page for this identifier may not exist yet.
Published yesterday. NVD backfills CPE data for days or weeks after publication, and OSV and the exploit indexes lag too. Scope and status here may change.
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.
CWE-863 · Incorrect authorization
No public exploit
Nothing published shows this CVE being exploited, which is not the same as ruling it out.
CVSS E:U
In RASP's scope, but nothing published names a fix and nothing published shows an exploit. Neither of the two things VRT can act on exists, which is a claim about the available evidence, not about the vulnerability.
| Decided by | no-exploit : With no fix path, a public exploit, or a CISA record of one |
|---|---|
| Finding | Resolved from QUEUED-FOR-REVIEW: this CVE affects a known product, but nothing published names a fix and nothing published shows an exploit. That is a statement about the evidence, not about the defect — it does not mean the vulnerability is unimportant or unreachable, only that neither of the two things VRT can act on exists. |
| URL | Tags |
|---|---|
| https://lists.apache.org/thread/psy1gj77jhf9y3lhph9yz4f5fovmkz7b | vendor-advisory |
| Published | 2026-09-14 | By the CVE Program. |
|---|---|---|
| NVD record modified | 2026-09-14 | NVD's own last-modified date for this record. |