CVE-2026-82428

/// Technical 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

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