CVE-2026-82440
HIGHDescription
Description Nimbus instantiates the class named by a topology's `topology.scheduler.strategy` when scheduling it. The allowlist intended to constrain that choice, `nimbus.scheduler.strategy.class.whitelist`, was treated as "allow any class" when unset, and it had no entry in the shipped `defaults.yaml`, so unset was the shipped state. An authenticated submitter could therefore cause Nimbus to instantiate any class on the Nimbus classpath that has a no-argument constructor. Storm's own production artifacts contain classes with side effects suitable for this: instantiating `org.apache.storm.testing.InProcessZookeeper` starts a ZooKeeper server with its own threads and sockets and nothing closes it, and `org.apache.storm.LocalCluster` behaves similarly. Repeated submissions therefore consume threads, sockets and memory in the most privileged daemon in the cluster. Mitigation Upgrade to 3.1.0, where an unset allowlist means the strategies shipped with Storm rather than any class. Note that this is a behaviour change: a cluster running an out-of-tree scheduler strategy without an explicit allowlist will have those topologies refused until the class is added to `nimbus.scheduler.strategy.class.whitelist`. The rejection message names the refused class and the configuration key. Users who cannot upgrade immediately should set `nimbus.scheduler.strategy.class.whitelist` explicitly to the strategies they intend to permit.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 40% of all known CVEs.
References
Related Vulnerabilities
Other CWE-470 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2021-21985 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2024-4990 | Critical | 9.1 | 80% | - | - |
| CVE-2024-0200 | High | 7.2 | 72% | - | Fix |
| CVE-2022-30287 | High | 8.0 | 69% | - | Fix |
| CVE-2026-82078 | Critical | 9.1 | 61% | KEV | Fix |
| CVE-2025-3600 | High | 7.5 | 26% | - | - |
Common questions
How do I fix CVE-2026-82440?
No published fix for CVE-2026-82440 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-82440 being actively exploited?
Not that we know of. CVE-2026-82440 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.45% is the estimated probability that it will be exploited in the next 30 days. That is higher than 40% of all scored CVEs.
How severe is CVE-2026-82440?
CVE-2026-82440 has a CVSS v3 base score of 8.1, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-82440
Markdown
[](https://tridentstack.com/cve/CVE-2026-82440)HTML
<a href="https://tridentstack.com/cve/CVE-2026-82440"><img src="https://tridentstack.com/cve/badge/CVE-2026-82440.svg" alt="CVE-2026-82440"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-11-12.