Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-82430. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-82430 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2026-82430. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with Not reported where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-82430 using CVSS null, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

Race Condition

CVE-2026-82430

CVE-2026-82430 — Apache Storm Worker Launcher: Local Privilege Escalation to Root via Container Command Files Chowned to the Tenant

Q: What is CVE-2026-82430?

CVE-2026-82430 is Apache Storm Worker Launcher: Local Privilege Escalation to Root via Container Command Files Chowned to the Tenant. The supplied enrichment data classifies it as Race Condition mapped to CWE-367 CWE-367.

Description When launching a Docker or OCI worker, the setuid-root `worker-launcher` first changes ownership of the entire worker directory to the untrusted topology user, and only afterwards reads and acts on the command file that the supervisor wrote into that same directory. The file is opened without `O_NOFOLLOW` and without re-verifying its owner, so between the ownership change and the read the tenant can replace its contents. For the Docker path the parsed command is executed with real uid 0, and the command sanitiser is not a privilege boundary: it admits `-v` with an arbitrary source, `--device`, `--cap-add`, `--security-opt`, `--user` and `--net`, and copies positional arguments through verbatim. A rewritten file therefore yields an attacker-authored, root-equivalent container invocation with the host filesystem available. For the OCI path the same rewrite window applies, and mount validation is structural only, with no source or destination allow-list, so arbitrary host paths can be bind-mounted read-write into the container. The `username` field of the command file is likewise attacker-settable and is checked only against non-root and minimum-uid rules, permitting execution as another tenant's uid. Mitigation Upgrade to 3.1.0, where the command file is validated before the ownership change and re-verified on open, and where mount sources and destinations are constrained by configuration. Users who cannot upgrade immediately should disable Docker and OCI worker isolation, or restrict topology submission on affected supervisors to trusted principals. Note that the launcher must be rebuilt and reinstalled after upgrading. Credit The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.

Published Sep 14, 2026Updated Sep 14, 2026Sources: NVD, Apache Software Foundation (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

ahead of 0% of scored CVEs

Affects

Apache

Apache Storm Worker Launcher

CVSS base

Unscored

no source published a base score

Remediation

The vendor's own words where we have them.

Upgrade Apache Storm Worker Launcher to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Apache	Apache Storm Worker Launcher	3.0.0 to < 3.1.0	Vulnerable

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-367 · Time-of-check Time-of-use (TOCTOU) Race Condition

Alter Execution Logic
Unexpected State
Modify Application Data
Modify Files or Directories

Mitigation: The most basic advice for TOCTOU vulnerabilities is to not perform a check before the use. This does not resolve the underlying issue of the execution of a function on a resource whose state and identity cannot be assured, but it does help to limit the false sense of security given by the check.

Weakness & attack patterns

CWE-367

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-29 · Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race ConditionsCAPEC-27 · Leveraging Race Conditions via Symbolic Links

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Initial · CVE published
Sep 14, 2026 · NVD
Added · GHSA-pjcp-2m43-fmv9 published (unknown)
Sep 14, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 14, 2026 · SOCRadar CTI

Source activity

Readings a source repeats on a schedule, counted rather than listed.

1×Tweets · 1 time tweeted.Sep 14, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Sep 14, 2026 · SOCRadar CTI
1×SVRS is calculatedSep 14, 2026 · SOCRadar CTI

References

3 on the record

lists.apache.org/thread/8d5pkn486p8vrz5klg6onk5r8k9sd9lv
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-82430
NVD
github.com/advisories/GHSA-pjcp-2m43-fmv9
Exploit, Third Party Advisory

Coverage

2 stories from the feeds we poll

Elsewhere on this site

Apacheevery CVE for this vendor
Race Conditionsame class
CWE-367other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-82430 is Apache Storm Worker Launcher: Local Privilege Escalation to Root via Container Command Files Chowned to the Tenant, a unscored vulnerability affecting Apache Storm Worker Launcher from Apache Software Foundation. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-82430. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-82430. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS null describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.