CVE-2026-82428
Deferred Deferred - Pending Action

Code Execution via Predictable Artifact Key in Apache Storm

Vulnerability report for CVE-2026-82428, 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 Dependency artifacts uploaded with `storm jar --artifacts` were stored under a blob key derived only from the Maven coordinate, for example `dep---.jar`. The key was therefore identical for every user of the cluster and predictable in advance. When the blob already existed, the uploader caught `KeyAlreadyExistsException` and silently reused it, with no check that the existing blob's content or owner matched the artifact the submitter had resolved. A user who uploaded a blob under such a key first therefore controlled the bytes that every later submitter of the same coordinate would receive on the worker classpath, resulting in code execution inside another tenant's topology. This affects deployments where more than one principal may create blobs and where the `--artifacts` dependency feature is used. Mitigation Upgrade to 3.1.0, where each uploaded artifact receives a key carrying a freshly generated UUID and a pre-existing blob is no longer silently reused. Note that the corrected key generation is on the SUBMITTING CLIENT, so upgrading the cluster alone does not close this; every client that runs `storm jar --artifacts` must also be upgraded. Operators should audit existing `dep-` blobs for unexpected owners before upgrading. Users who cannot upgrade immediately should avoid the `--artifacts` mechanism in multi-tenant clusters and distribute dependencies inside the topology jar instead. Credit The ASF -- found 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 3 associated CPEs
Vendor Product Version / Range
apache storm 3.1.0
apache storm From 3.1.0 (exc)
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 involves predictable blob keys for dependency artifacts in Apache Storm. When uploading artifacts with `storm jar --artifacts`, the blob key was derived only from the Maven coordinate, making it identical and predictable for all users. If a blob already existed, it was silently reused without verifying content or ownership, allowing a malicious user to replace dependencies for other tenants.

Detection Guidance

Check for duplicate blob keys under the dep---.jar pattern in your storage system. Audit existing dep- blobs for unexpected owners or mismatched content before upgrading. Look for multiple users uploading artifacts with the same Maven coordinate.

Impact Analysis

This vulnerability allows code execution within another tenant's topology. An attacker could upload malicious dependencies under a predictable blob key, which would then be downloaded and executed by other users submitting the same Maven coordinate. This affects multi-tenant clusters where multiple principals can create blobs.

Compliance Impact

This vulnerability could lead to unauthorized code execution within another tenant's environment, potentially violating data confidentiality and integrity requirements under GDPR and HIPAA. The lack of tenant isolation in dependency artifact handling may result in unauthorized access to sensitive data processed by affected topologies.

Mitigation Strategies

Upgrade all clients running storm jar --artifacts to version 3.1.0 or later. Avoid using the --artifacts mechanism in multi-tenant clusters until all clients are upgraded. Distribute dependencies inside the topology jar as a temporary workaround.

Chat Assistant

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

EPSS Chart