High [CVE-2026-82429] Apache Storm: Description The setuid-root `worker-launcher` binary adjusts ownership and permissions of worker directories by walking the tree with FTS and calling `lchown` and `chmod` on each entry's full pathname while running with an effective uid of 0
This high-severity Apache Software Foundation advisory covers CVE-2026-82429; related products: Apache Storm.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Get an email when Apache Software Foundation Data & Analytics (Spark/Hadoop/Gravitino) publishes the next one.
See Apache Software Foundation Data & Analytics (Spark/Hadoop/Gravitino)'s last 90 days of advisories first. Then choose the free weekly digest, or a free month of real-time alerts with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
Summary
The setuid-root `worker-launcher` binary adjusts ownership and permissions of worker directories by walking the tree with FTS and calling `lchown` and `chmod` on each entry's full pathname while running with an
effective uid of 0. Both syscalls re-resolve the path at the time of the call, after FTS has classified the
entry, and the trees being walked are owned and writable by the untrusted topology user.
A tenant running code on a supervisor node could therefore replace an intermediate directory component with a symbolic link between classification and the privileged operation, redirecting the root-owned `lchown` or
`chmod` at an arbitrary file on the host. The operation is repeatable at will, since crashing a worker
forces a relaunch and blob updates re-run the walk, so a failed attempt costs the attacker nothing.
This crosses the boundary that `supervisor.run.worker.as.user` and container isolation are intended to enforce.
It is the same defect class as the Hadoop container-executor issues from which this code derives.
Affected product named by the advisory: Apache Storm.
- Apache Storm Worker Launcher 3.0.0 before 3.1.0
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
Mitigation checklist
- A tenant running code on a supervisor node could therefore replace an intermediate directory component with a symbolic link between classification and the privileged operation, redirecting the root-owned `lchown` or `chmod` at an arbitrary file on the host.
- Mitigation Upgrade to 3.1.0, where the privileged walk operates on file descriptors it has already stat'd rather than on pathnames re-resolved at call time.
- Users who cannot upgrade immediately should not run untrusted topology code on supervisors configured with `supervisor.run.worker.as.user`, since the launcher is the boundary being crossed.
Official advisory · high-confidence parse· fetched 2 months ago·verify at source
More Apache Software Foundation advisories
- CVE-2026-82427Sep 14, 2026Apache Storm: Description A topology's `topology.blobstore.map` lets the submitter choose
- CVE-2026-82428Sep 14, 2026Apache Storm: Description Dependency artifacts uploaded with `storm jar --artifacts` were
- CVE-2026-82430Sep 14, 2026Apache Storm: Description When launching a Docker or OCI worker, the setuid-root
- CVE-2026-82431Sep 14, 2026Apache Storm: Description `SimpleACLAuthorizer` evaluated the user-level command set
- CVE-2026-82433Sep 14, 2026Apache Storm: Description `getNimbusConf` returned the complete daemon configuration
- CVE-2026-82432Sep 14, 2026Apache Storm: Description Nimbus validated `topology.blobstore.map` against the calling
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 34 official vendor sources and 160+ reviewed platform categories.
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.