CVE-2026-82428: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Apache Software Foundation Apache Storm Client
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.
AI Analysis
Technical Summary
The vulnerability in Apache Storm Client (CVE-2026-82428) involves improper limitation of a pathname to a restricted directory (CWE-22) due to predictable blob keys derived only from Maven coordinates when uploading dependency artifacts via 'storm jar --artifacts'. Because the blob key is the same for all users, a malicious user can upload a crafted artifact that subsequent users will receive, enabling code execution in other tenants' topologies. This affects multi-tenant deployments using the '--artifacts' feature. The fix in version 3.1.0 introduces unique UUID-based keys per upload and prevents silent reuse of existing blobs. Upgrading both the cluster and all clients that use 'storm jar --artifacts' is necessary. Operators should audit existing blobs for unexpected owners and avoid using '--artifacts' in multi-tenant setups if immediate upgrade is not possible.
Potential Impact
This vulnerability allows an attacker who can upload artifacts to a multi-tenant Apache Storm cluster to execute arbitrary code within other tenants' topologies by controlling the artifact content loaded on their worker classpath. This compromises tenant isolation and can lead to unauthorized code execution and potential data compromise within the cluster.
Mitigation Recommendations
Upgrade Apache Storm to version 3.1.0 or later, where artifact keys include a unique UUID and existing blobs are not silently reused. It is critical to upgrade both the cluster and all clients that run 'storm jar --artifacts' to fully mitigate the issue. Operators should audit existing 'dep-' blobs for unexpected owners before upgrading. If immediate upgrade is not feasible, avoid using the '--artifacts' feature in multi-tenant clusters and instead distribute dependencies inside the topology jar.
CVE-2026-82428: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in Apache Software Foundation Apache Storm Client
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.
Affected software
Apache Software Foundation
Apache Storm Client
pkg:maven/Apache Software Foundation/org.apache.storm:storm-clientRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Apache Storm Client (CVE-2026-82428) involves improper limitation of a pathname to a restricted directory (CWE-22) due to predictable blob keys derived only from Maven coordinates when uploading dependency artifacts via 'storm jar --artifacts'. Because the blob key is the same for all users, a malicious user can upload a crafted artifact that subsequent users will receive, enabling code execution in other tenants' topologies. This affects multi-tenant deployments using the '--artifacts' feature. The fix in version 3.1.0 introduces unique UUID-based keys per upload and prevents silent reuse of existing blobs. Upgrading both the cluster and all clients that use 'storm jar --artifacts' is necessary. Operators should audit existing blobs for unexpected owners and avoid using '--artifacts' in multi-tenant setups if immediate upgrade is not possible.
Potential Impact
This vulnerability allows an attacker who can upload artifacts to a multi-tenant Apache Storm cluster to execute arbitrary code within other tenants' topologies by controlling the artifact content loaded on their worker classpath. This compromises tenant isolation and can lead to unauthorized code execution and potential data compromise within the cluster.
Mitigation Recommendations
Upgrade Apache Storm to version 3.1.0 or later, where artifact keys include a unique UUID and existing blobs are not silently reused. It is critical to upgrade both the cluster and all clients that run 'storm jar --artifacts' to fully mitigate the issue. Operators should audit existing 'dep-' blobs for unexpected owners before upgrading. If immediate upgrade is not feasible, avoid using the '--artifacts' feature in multi-tenant clusters and instead distribute dependencies inside the topology jar.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-08-29T10:09:55.176Z
- State
- PUBLISHED
Threat ID: 6aa8057055bf5e2cf52f81bd
Added to database: 09/14/2026, 14:32:16 UTC
Last enriched: 09/14/2026, 14:48:25 UTC
Last updated: 09/14/2026, 18:06:05 UTC
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.