CVE-2026-82426
Deferred Deferred - Pending Action

Path Traversal in Apache Storm Nimbus

Vulnerability report for CVE-2026-82426, 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 Nimbus accepted the `uploadedJarLocation` argument of `submitTopology` / `submitTopologyWithOpts` as a server-side path and opened it directly, without checking that it referred to a file the caller had actually uploaded. The intended flow is that a client first calls `beginFileUpload`, which returns a path inside the Nimbus inbox, and uploads the jar in chunks to that location; nothing bound submission to that flow, and the `uploaders` map populated by `beginFileUpload` was never consulted at submit time. An authenticated user with topology submission rights could therefore submit any path readable by the Nimbus daemon user as their topology jar. Nimbus copied the file into the topology's jar blob, and the blob ACL grants the submitting subject read access, so the contents could then be retrieved with the ordinary blob download RPCs. Candidate targets include the Nimbus Kerberos keytab, Thrift and UI TLS private keys, and `storm.yaml` with the ZooKeeper authentication payload. Possession of the Nimbus keytab turns an ordinary tenant into a cluster administrator. In a deployment configured as the documentation recommends, submission is available to every authenticated principal when `nimbus.users` is unset, so no elevated privilege is required. Mitigation Upgrade to 3.1.0, where the submitted location is canonicalised and must resolve inside the Nimbus inbox. Users who cannot upgrade immediately should restrict topology submission to trusted principals via `nimbus.users` or `nimbus.groups`, and should treat any file readable by the Nimbus daemon user as potentially exposed to submitters: rotate the Nimbus keytab and any TLS private keys or ZooKeeper credentials reachable from that account. Local mode is unaffected. Credit Independently reported to the Apache Storm PMC by n0mi1k, with a proof of concept. Also found by the ASF using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.

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 2 associated CPEs
Vendor Product Version / Range
apache storm 3.1.0
apache storm to 3.1.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in Apache Storm Nimbus versions before 3.1.0 allows an authenticated user with topology submission rights to read arbitrary files on the Nimbus server by exploiting an unvalidated uploaded JAR location parameter. The flaw occurs because Nimbus accepts a server-side path in submitTopology without checking if it matches the legitimate upload location from beginFileUpload.

Detection Guidance

To detect this vulnerability, check if Nimbus versions are below 3.1.0. Review topology submission logs for unauthorized file paths in uploadedJarLocation. Inspect blob downloads for unexpected access to sensitive files like keytabs or storm.yaml.

Impact Analysis

An attacker could read sensitive files like the Nimbus Kerberos keytab, TLS private keys, or storm.yaml containing ZooKeeper credentials. If the Nimbus keytab is compromised, an ordinary tenant could gain cluster administrator privileges. The impact includes potential full cluster compromise and exposure of credentials.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive files such as Kerberos keytabs, TLS private keys, or configuration files containing credentials like ZooKeeper authentication payloads. Such access may violate compliance requirements under GDPR (data protection) or HIPAA (health data security) by exposing confidential information or enabling unauthorized system access.

Mitigation Strategies

Upgrade Apache Storm Nimbus to version 3.1.0 or later to fix the vulnerability. If immediate upgrade is not possible, restrict topology submission rights to trusted principals using nimbus.users or nimbus.groups settings. Rotate sensitive credentials like the Nimbus keytab, TLS private keys, and ZooKeeper credentials as they may have been exposed.

Chat Assistant

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

EPSS Chart