Skip to content
VulniPulse
UnratedApache Software Foundation Updated

Advisory [CVE-2026-82428] Apache Storm: Description Dependency artifacts uploaded with `storm jar --artifacts` were stored under a blob key derived only from the Maven coordinate, for example `dep---.jar`

This security Apache Software Foundation advisory covers CVE-2026-82428 affecting Apache Storm.

CVE-2026-82428 Published Sep 14, 2026Updated by vendor Sep 14, 2026
Related products & platforms
Apache Software FoundationUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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.

Affected product named by the advisory: Apache Storm.

Affected versions
  • Apache Storm Client 3.0.0 before 3.1.0

Official advisory · medium-confidence parse· fetched 3 hours ago·verify at source

Fixed versions
  • 3.1.0

Official advisory · medium-confidence parse· fetched 3 hours ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • 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.
  • Users who cannot upgrade immediately should avoid the `--artifacts` mechanism in multi-tenant clusters and distribute dependencies inside the topology jar instead.

Official advisory · medium-confidence parse· fetched 3 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.