Critical [CVE-2026-82441] Description A submitted topology carries two lists of blobstore keys, `dependency_jars` and `dependency_artifacts`, which the client fills in after uploading the corresponding blobs
This critical-severity Apache Software Foundation advisory covers CVE-2026-82441; related products: Apache Storm Nimbus.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Get an email when Apache Software Foundation publishes the next one.
See Apache Software Foundation's last 90 days of advisories first. Then choose the free weekly digest, or a free month of real-time alerts with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
Summary
A submitted topology carries two lists of blobstore keys, `dependency_jars` and `dependency_artifacts`, which the client fills in after uploading the corresponding blobs.
Nimbus performed no validation of their contents on the submission path, yet acts on them in two places.
During cleanup of a finished topology, Nimbus deletes the keys named in those lists, and the deletion is performed as the Nimbus subject, for which the blobstore short-circuits its ACL check.
A submitter who listed a key belonging to another topology, such as its `-stormjar.jar`, could therefore cause
that blob to be deleted when their own topology was cleaned up.
Separately, on acquiring leadership a Nimbus compares the dependency keys of all active topologies against the blobstore contents and surrenders leadership if any is missing.
A single key that does not exist, on a single active topology, therefore causes every Nimbus to acquire leadership, surrender it and requeue
indefinitely, leaving the cluster without a leader and unable to schedule, clean up or accept submissions.
Affected product named by the advisory: Apache Storm Nimbus.
- Apache Storm Nimbus 3.0.0 before 3.1.0
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
Mitigation checklist
- Mitigation Upgrade to 3.1.0, where a submission is refused unless every entry in both lists is a dependency blob key and exists in the blobstore.
- Note that this validates new submissions only; a topology stored by an affected version with an invalid list is unaffected by the upgrade.
- An operator whose cluster is failing to retain a leader should inspect the Nimbus log for the dependency keys reported as missing and remove or resubmit the topology naming them.
- Users who cannot upgrade immediately should restrict topology submission to trusted principals.
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
More Apache Software Foundation advisories
- CVE-2026-114442Nov 3, 2026Apache HertzBeat versions 1.7.1, 1.7.2, 1.7.3, 1.8.0, and 1.9.0 have incomplete XPath
- CVE-2026-119641Nov 3, 2026** UNSUPPORTED WHEN ASSIGNED ** Improper input validation vulnerability in Apache Oozie
- CVE-2026-119724Nov 3, 2026** UNSUPPORTED WHEN ASSIGNED ** Improper restriction of recursive entity references
- CVE-2026-111959Nov 2, 2026Out-of-bounds read vulnerability in Apache Arrow Rust (`arrow` crate), from version 33.0.0
- CVE-2026-114364Nov 2, 2026Apache Syncope SQL injection
- CVE-2026-113687Nov 2, 2026Improper isolation or compartmentalization vulnerability in Apache Syncope
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 34 official vendor sources and 160+ reviewed platform categories.
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.