CVE-2026-82441

/// Technical description

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. 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

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References