CVE-2026-82441
Deferred Deferred - Pending Action

Path Traversal in Apache Storm Nimbus

Vulnerability report for CVE-2026-82441, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-14

Last updated on: 2026-09-14

Assigner: Apache Software Foundation

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 cluster without a leader and unable to schedule, clean up or accept submissions. 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. Credit This issue was discovered by rzo1 while investigating an unrelated blobstore defect.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-14
Last Modified
2026-09-14
Generated
2026-09-15
AI Q&A
2026-09-14
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
apache nimbus 3.1.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-20 The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Apache Nimbus allows a submitter to list blobstore keys belonging to other topologies in their submission. During cleanup, Nimbus deletes these keys as the Nimbus subject, bypassing access control checks. This can cause unintended deletion of blobs from other topologies. Additionally, if a dependency key is missing, Nimbus surrenders leadership repeatedly, leaving the cluster leaderless and unable to perform tasks like scheduling or cleanup.

Detection Guidance

Check Nimbus logs for missing dependency keys during leadership acquisition failures. Look for errors indicating non-existent blobstore keys in active topologies. Verify if any topology submissions contain invalid or cross-tenant blobstore keys in dependency_jars or dependency_artifacts lists.

Impact Analysis

If exploited, this vulnerability can lead to data loss by deleting blobs from other topologies. It can also cause cluster instability by preventing Nimbus from retaining a leader, disrupting normal operations like job scheduling and cleanup. Unpatched clusters may experience repeated leadership changes and operational failures.

Compliance Impact

This vulnerability could impact compliance with GDPR and HIPAA by enabling unauthorized data deletion and disrupting service availability. Under GDPR, unauthorized deletion of data may violate integrity and availability principles, while HIPAA requires safeguards against unauthorized access or destruction of protected health information. The denial-of-service effect could also prevent timely processing of sensitive data.

Mitigation Strategies

Upgrade to Apache Storm Nimbus version 3.1.0 or later where submission validation is enforced. If upgrading is not possible, restrict topology submission to trusted principals only.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-82441. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart