AI and data stack advisories

Severe, 6 weeks2431Projects328

2431 severe, 6 weeks · 328 projects

Description Nimbus instantiates the class named by a topology's...

Apache Software Foundation

CVE-2026-82440 · Published Nov 9, 2026 · updated Nov 12, 2026

High8.1
Fix: upgrade to 3.1.0 or later

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...

Affected versions

PackageAffectedFixed in
Apache Storm Nimbus
Product
>= 3.0.0, < 3.1.03.1.0
Details and references

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.

CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Severity from
CISA (its enrichment of the CVE record)
Weakness
CWE-470

More Apache Software Foundation advisories

All Apache Software Foundation