CVE-2026-82440: Apache Storm Nimbus · Reflection Injection
Affects Apache Storm NimbusSource CVE Database V5
Not known to be exploited : upgrade to 3.1.0 soon.
Data as of 9 Nov 2026, 10:35 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 3.1.0
Exploitation evidence
Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade Apache Storm Nimbus and org.apache.storm/storm-client to 3.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apache Storm Nimbusorg.apache.storm:storm-client | Affected
| Fixed in
|
Mavenorg.apache.storm/storm-clientpkg:maven/org.apache.storm/storm-clientOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Apache Storm Nimbus to version 3.1.0 or later, where the default behavior restricts scheduler strategy instantiation to Storm's built-in classes if the allowlist is unset. For users unable to upgrade immediately, explicitly set 'nimbus.scheduler.strategy.class.whitelist' to include only the intended scheduler strategy classes to prevent unauthorized class instantiation.
Description
Apache Storm Nimbus versions 3.0.0 up to but not including 3.1.0 have a reflection injection vulnerability due to an unset allowlist for topology scheduler strategies. This allows an authenticated submitter to cause Nimbus to instantiate any class on its classpath with a no-argument constructor, potentially leading to resource exhaustion by starting unwanted threads and sockets. The issue is fixed in version 3.1.0 by changing the default behavior to restrict instantiation to Storm's shipped strategies unless explicitly allowed.