Read the docs

Unchecked scheduler class instantiation in Apache Storm Nimbus

Priority LOW 36CWE-470Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA.

Summary

Apache Storm Nimbus from 3.0.0 before 3.1.0 instantiates the class named by a topology's topology.scheduler.strategy setting. The allowlist meant to restrict that class treats an unset value as allowing any class, and the shipped defaults leave it unset. An authenticated submitter can make Nimbus instantiate any class on its classpath that has a no-argument constructor, such as a class that starts a server with threads and sockets that are never closed. Repeated submissions can then consume threads, sockets and memory in the most privileged daemon in the cluster, as described in CWE-470.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00451 39th percentileScored 2026-11-16
Fix Fixed Apache Storm Nimbus (Apache Software Foundation): 3.1.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
ApacheApache Storm Nimbus3.0.0 to before 3.1.03.1.0Patch availableCNA
  • Apache Storm Nimbus VendorApache Affected 3.0.0 to before 3.1.0 Fixed in 3.1.0 Patch available CNA

Remediation

Upgrade Apache Storm Nimbus to 3.1.0, where an unset allowlist permits only the strategies shipped with Storm. Clusters that run an out-of-tree scheduler strategy must add its class to nimbus.scheduler.strategy.class.whitelist, or those topologies are refused. Users who cannot upgrade immediately should set nimbus.scheduler.strategy.class.whitelist explicitly to the strategies they intend to permit.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · CNA Apache Storm Nimbus (Apache Software Foundation) Fixed in 3.1.0

Timeline

  1. 2026-11-09 Threatist record created from CVE-2026-82440
  2. 2026-11-09 Alias added: GHSA-p7mh-274j-m4mq
  3. 2026-11-12 CVSS score added · CISA ADP
  4. 2026-11-12 CISA SSVC decision points changed

References

  • TI-2025-18529 Path equivalence in Apache Tomcat allows code execution via PUT KEVCVSS 3.1CRITICAL 10.0
  • TI-2024-30292 Forced browsing in Apache OFBiz bypasses controller-view authorization KEVCVSS 3.1CRITICAL 9.8
  • TI-2024-26062 Incorrect authorization in Apache OFBiz exposes screen rendering code KEVCVSS 3.1CRITICAL 9.8
  • TI-2024-21190 Path traversal in Apache OFBiz leads to remote code execution KEVCVSS 3.1CRITICAL 9.8
  • TI-2024-18186 Remote command execution in Apache HugeGraph-Server via Gremlin KEVCVSS 3.1CRITICAL 9.8
  • TI-2023-25106 Apache ActiveMQ OpenWire deserialization allows remote code execution KEVCVSS 3.1CRITICAL 10.0
See all 4172 →

Sources