{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-82440", "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "state": "PUBLISHED", "assignerShortName": "apache", "dateReserved": "2026-08-29T10:42:00.358Z", "datePublished": "2026-11-09T10:01:57.147Z", "dateUpdated": "2026-11-09T10:13:16.862Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "shortName": "apache", "dateUpdated": "2026-11-09T10:01:57.147Z"}, "title": "Apache Storm Nimbus: Submitter-Controlled Class Instantiation in Nimbus via a Fail-Open Scheduler Strategy Allowlist", "problemTypes": [{"descriptions": [{"description": "CWE-470 Use of Externally-Controlled input to select classes or code ('unsafe reflection')", "lang": "en", "cweId": "CWE-470", "type": "CWE"}]}], "source": {"discovery": "UNKNOWN"}, "affected": [{"vendor": "Apache Software Foundation", "product": "Apache Storm Nimbus", "packageURL": "pkg:maven/org.apache.storm/storm-client", "versions": [{"status": "affected", "version": "3.0.0", "lessThan": "3.1.0", "versionType": "semver"}], "defaultStatus": "unaffected", "collectionURL": "https://repo.maven.apache.org/maven2", "packageName": "org.apache.storm:storm-client"}], "descriptions": [{"value": "Description\n\nNimbus instantiates the class named by a topology's `topology.scheduler.strategy` when scheduling it. The\nallowlist intended to constrain that choice, `nimbus.scheduler.strategy.class.whitelist`, was treated as\n\"allow any class\" when unset, and it had no entry in the shipped `defaults.yaml`, so unset was the shipped\nstate. An authenticated submitter could therefore cause Nimbus to instantiate any class on the Nimbus\nclasspath that has a no-argument constructor.\n\nStorm's own production artifacts contain classes with side effects suitable for this: instantiating\n`org.apache.storm.testing.InProcessZookeeper` starts a ZooKeeper server with its own threads and sockets\nand nothing closes it, and `org.apache.storm.LocalCluster` behaves similarly. Repeated submissions\ntherefore consume threads, sockets and memory in the most privileged daemon in the cluster.\n\nMitigation\n\nUpgrade to 3.1.0, where an unset allowlist means the strategies shipped with Storm rather than any class.\n\nNote that this is a behaviour change: a cluster running an out-of-tree scheduler strategy without an\nexplicit allowlist will have those topologies refused until the class is added to\n`nimbus.scheduler.strategy.class.whitelist`. The rejection message names the refused class and the\nconfiguration key.\n\nUsers who cannot upgrade immediately should set `nimbus.scheduler.strategy.class.whitelist` explicitly to\nthe strategies they intend to permit.", "lang": "en", "supportingMedia": [{"type": "text/html", "base64": false, "value": "<b>Description</b><br><br>Nimbus instantiates the class named by a topology's `topology.scheduler.strategy` when scheduling it. The<br>allowlist intended to constrain that choice, `nimbus.scheduler.strategy.class.whitelist`, was treated as<br>\"allow any class\" when unset, and it had no entry in the shipped `defaults.yaml`, so unset was the shipped<br>state. An authenticated submitter could therefore cause Nimbus to instantiate any class on the Nimbus<br>classpath that has a no-argument constructor.<br><br>Storm's own production artifacts contain classes with side effects suitable for this: instantiating<br>`org.apache.storm.testing.InProcessZookeeper` starts a ZooKeeper server with its own threads and sockets<br>and nothing closes it, and `org.apache.storm.LocalCluster` behaves similarly. Repeated submissions<br>therefore consume threads, sockets and memory in the most privileged daemon in the cluster.<br><br><div><b>Mitigation</b><br><br>Upgrade to 3.1.0, where an unset allowlist means the strategies shipped with Storm rather than any class.<br><br>Note that this is a behaviour change: a cluster running an out-of-tree scheduler strategy without an<br>explicit allowlist will have those topologies refused until the class is added to<br>`nimbus.scheduler.strategy.class.whitelist`. The rejection message names the refused class and the<br>configuration key.<br><br>Users who cannot upgrade immediately should set `nimbus.scheduler.strategy.class.whitelist` explicitly to<br>the strategies they intend to permit.</div>"}]}], "references": [{"url": "https://lists.apache.org/thread.html/hxcyk1vg9qx8bzos8g3kx91nz8d23jgt", "tags": ["vendor-advisory"]}], "metrics": [{"other": {"type": "Textual description of severity", "content": {"text": "moderate"}}, "scenarios": [{"lang": "en", "value": "GENERAL"}]}], "credits": [{"lang": "en", "value": "The ASF using Claude Agents", "type": "finder"}], "x_generator": {"engine": "Vulnogram 1.0.3"}}, "adp": [{"title": "CVE Program Container", "references": [{"url": "http://www.openwall.com/lists/oss-security/2026/11/09/2"}], "providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2026-11-09T10:13:16.862Z"}}]}}

{}

{"affected": [{"affectedData": [{"collectionURL": "https://repo.maven.apache.org/maven2", "defaultStatus": "unaffected", "packageName": "org.apache.storm:storm-client", "packageURL": "pkg:maven/org.apache.storm/storm-client", "product": "Apache Storm Nimbus", "vendor": "Apache Software Foundation", "versions": [{"lessThan": "3.1.0", "status": "affected", "version": "3.0.0", "versionType": "semver"}]}], "source": "security@apache.org"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "Description\n\nNimbus instantiates the class named by a topology's `topology.scheduler.strategy` when scheduling it. The\nallowlist intended to constrain that choice, `nimbus.scheduler.strategy.class.whitelist`, was treated as\n\"allow any class\" when unset, and it had no entry in the shipped `defaults.yaml`, so unset was the shipped\nstate. An authenticated submitter could therefore cause Nimbus to instantiate any class on the Nimbus\nclasspath that has a no-argument constructor.\n\nStorm's own production artifacts contain classes with side effects suitable for this: instantiating\n`org.apache.storm.testing.InProcessZookeeper` starts a ZooKeeper server with its own threads and sockets\nand nothing closes it, and `org.apache.storm.LocalCluster` behaves similarly. Repeated submissions\ntherefore consume threads, sockets and memory in the most privileged daemon in the cluster.\n\nMitigation\n\nUpgrade to 3.1.0, where an unset allowlist means the strategies shipped with Storm rather than any class.\n\nNote that this is a behaviour change: a cluster running an out-of-tree scheduler strategy without an\nexplicit allowlist will have those topologies refused until the class is added to\n`nimbus.scheduler.strategy.class.whitelist`. The rejection message names the refused class and the\nconfiguration key.\n\nUsers who cannot upgrade immediately should set `nimbus.scheduler.strategy.class.whitelist` explicitly to\nthe strategies they intend to permit."}], "id": "CVE-2026-82440", "lastModified": "2026-11-09T10:17:11.797", "metrics": {}, "published": "2026-11-09T10:17:11.797", "references": [{"source": "security@apache.org", "url": "https://lists.apache.org/thread.html/hxcyk1vg9qx8bzos8g3kx91nz8d23jgt"}], "sourceIdentifier": "security@apache.org", "vulnStatus": "Received", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-470"}], "source": "security@apache.org", "type": "Primary"}]}

{}

{}