CVE-2026-82440 — CWE-470
CVE-2026-82440 is a HIGH severity security vulnerability (CWE-470) (CVSS 8.1/10) affecting affected software system. Technical vector analysis shows that an attacker can exploit this flaw remotely over the network with low-privileged access (PR:L) with zero user interaction (UI:N), causing high-impact service disruption (A:H).
📄 Official NVD / MITRE Original Record Text
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.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-82440
CVSS 8.1/10 · HIGH · 09.11.2026
CWE: CWE-470
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
Summary: 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 …
⚡ ATTACK CHAIN
Remotely over internet | low-privilege account | no user interaction | low complexity.
🌍 REAL WORLD IMPACT
Data can be modified or deleted; service can be completely taken down.
🛡️ REMEDIATION
→ Apply the vendor-released patch immediately.
→ Add WAF rule, create IDS alert for anomalous traffic.
⚠️ URGENCY
⚠️ Planned maintenance (2 weeks).
────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]