{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-82441", "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "state": "PUBLISHED", "assignerShortName": "apache", "dateReserved": "2026-08-29T10:43:56.799Z", "datePublished": "2026-09-14T13:58:56.249Z", "dateUpdated": "2026-09-14T14:13:47.952Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "shortName": "apache", "dateUpdated": "2026-09-14T13:58:56.249Z"}, "title": "Apache Storm Nimbus: Cross-Tenant Blob Deletion and Cluster Denial of Service via Unvalidated Topology Dependency Keys", "problemTypes": [{"descriptions": [{"description": "CWE-20 Improper input validation", "lang": "en", "cweId": "CWE-20", "type": "CWE"}]}, {"descriptions": [{"description": "CWE-639 Authorization Bypass Through User-Controlled Key", "lang": "en", "cweId": "CWE-639", "type": "CWE"}]}], "source": {"discovery": "UNKNOWN"}, "affected": [{"vendor": "Apache Software Foundation", "product": "Apache Storm Nimbus", "collectionURL": "https://repo.maven.apache.org/maven2", "packageName": "org.apache.storm:storm-server", "versions": [{"status": "affected", "version": "3.0.0", "lessThan": "3.1.0", "versionType": "semver"}], "defaultStatus": "unaffected"}], "descriptions": [{"value": "Description\n\nA submitted topology carries two lists of blobstore keys, `dependency_jars` and `dependency_artifacts`,\nwhich the client fills in after uploading the corresponding blobs. Nimbus performed no validation of their\ncontents on the submission path, yet acts on them in two places.\n\nDuring cleanup of a finished topology, Nimbus deletes the keys named in those lists, and the deletion is\nperformed as the Nimbus subject, for which the blobstore short-circuits its ACL check. A submitter who\nlisted a key belonging to another topology, such as its `-stormjar.jar`, could therefore cause\nthat blob to be deleted when their own topology was cleaned up.\n\nSeparately, on acquiring leadership a Nimbus compares the dependency keys of all active topologies against\nthe blobstore contents and surrenders leadership if any is missing. A single key that does not exist, on a\nsingle active topology, therefore causes every Nimbus to acquire leadership, surrender it and requeue\nindefinitely, leaving the cluster without a leader and unable to schedule, clean up or accept submissions.\n\nMitigation\n\nUpgrade to 3.1.0, where a submission is refused unless every entry in both lists is a dependency blob key\nand exists in the blobstore.\n\nNote that this validates new submissions only; a topology stored by an affected version with an invalid list\nis unaffected by the upgrade. An operator whose cluster is failing to retain a leader should inspect the\nNimbus log for the dependency keys reported as missing and remove or resubmit the topology naming them.\n\nUsers who cannot upgrade immediately should restrict topology submission to trusted principals.\n\nCredit\n\nThis issue was discovered by rzo1 while investigating an unrelated blobstore defect.", "lang": "en", "supportingMedia": [{"type": "text/html", "base64": false, "value": "<b>Description</b><br><br>A submitted topology carries two lists of blobstore keys, `dependency_jars` and `dependency_artifacts`,<br>which the client fills in after uploading the corresponding blobs. Nimbus performed no validation of their<br>contents on the submission path, yet acts on them in two places.<br><br>During cleanup of a finished topology, Nimbus deletes the keys named in those lists, and the deletion is<br>performed as the Nimbus subject, for which the blobstore short-circuits its ACL check. A submitter who<br>listed a key belonging to another topology, such as its `-stormjar.jar`, could therefore cause<br>that blob to be deleted when their own topology was cleaned up.<br><br>Separately, on acquiring leadership a Nimbus compares the dependency keys of all active topologies against<br>the blobstore contents and surrenders leadership if any is missing. A single key that does not exist, on a<br>single active topology, therefore causes every Nimbus to acquire leadership, surrender it and requeue<br>indefinitely, leaving the cluster without a leader and unable to schedule, clean up or accept submissions.<br><br><b>Mitigation</b><br><br>Upgrade to 3.1.0, where a submission is refused unless every entry in both lists is a dependency blob key<br>and exists in the blobstore.<br><br>Note that this validates new submissions only; a topology stored by an affected version with an invalid list<br>is unaffected by the upgrade. An operator whose cluster is failing to retain a leader should inspect the<br>Nimbus log for the dependency keys reported as missing and remove or resubmit the topology naming them.<br><br>Users who cannot upgrade immediately should restrict topology submission to trusted principals.<br><br><b>Credit</b><br><br>This issue was discovered by rzo1 while investigating an unrelated blobstore defect.<br>"}]}], "references": [{"url": "https://lists.apache.org/thread/qzh245bczoxw4mfnyvrj3dj2crtzdso8", "tags": ["vendor-advisory"]}], "metrics": [{"other": {"type": "Textual description of severity", "content": {"text": "moderate"}}, "scenarios": [{"lang": "en", "value": "GENERAL"}]}], "credits": [{"lang": "en", "value": "rzo1", "type": "finder"}], "x_generator": {"engine": "Vulnogram 1.0.3"}}, "adp": [{"title": "CVE Program Container", "references": [{"url": "http://www.openwall.com/lists/oss-security/2026/09/13/19"}], "providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2026-09-14T14:13:47.952Z"}}]}}

{}

{}

{}

{}