SEPTEMBER 15, 2026
Live Feed
Back to database
Case File

CVE-2026-82429

HIGH · CVSS 7.8

Source: NVD + CISA KEV + EPSS · Published 2026-09-14 · Last synced 2026-09-15

CyberRota Analysis

AI-Generated

The `worker-launcher` binary in Apache and Java is vulnerable due to improper handling of directory permissions, allowing an untrusted user to exploit symbolic links to redirect privileged operations like `lchown` and `chmod` to arbitrary files on the host system. This vulnerability can be repeatedly exploited by a tenant running code on a supervisor node, potentially leading to unauthorized access and manipulation of sensitive files. Organizations using affected versions should prioritize upgrading to version 3.1.0 or later, and in the interim, avoid running untrusted code on supervisor nodes configured with `supervisor.run.worker.as.user`.

CVE
CVE-2026-82429
Severity
HIGH
CVSS
7.8
EPSS
N/A
Apache Java

Original NVD Description

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. 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. 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. Note that the launcher must be rebuilt and reinstalled after upgrading; replacing the Java artifacts alone is not sufficient. Credit The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.