GHSA-45m3-3j6g-xv67
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain valid Nimbus authentication credentials
-
DeliveryConnect to Nimbus thrift API from any client
-
ExploitSimpleACLAuthorizer finds nimbus.users empty and returns early
-
ExecutionGroup restriction check in nimbus.groups is never evaluated
-
PersistAttacker receives full user-level authorization
-
ImpactSubmit arbitrary topology or exfiltrate getNimbusConf data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization logic validation
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires three concurrent conditions: (1) |
| Impact | No CVSS vector or EPSS score was provided in the input; all metric assessments below are independently derived from the advisory description. Real-world risk is significant within the specific affected deployment pattern but constrained by configuration prerequisites. The bypass only manifests when an operator has explicitly set |
| Exploit ScenarioDerived | An authenticated Nimbus user whose principal is not a member of any configured group connects to the cluster thrift API. Because |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 13, 2026
Authorization bypass in Apache Storm Client 3.0.0 permits any authenticated Nimbus principal to perform unrestricted user-level cluster operations when access control is configured via nimbus.groups alone. The SimpleACLAuthorizer evaluates user-level commands by returning early with a grant when nimbus.users is empty, never reaching the group evaluation branch, so group restrictions are silently ignored. Operators who followed the documented nimbus.groups-only access control pattern in docs/SECURITY.md would believe their cluster was restricted while every authenticated credential held full permission to submit topologies, upload files, and retrieve Nimbus configuration. No public exploit code exists and no CISA KEV listing is present at time of analysis.
RemediationAI
Upgrade org.apache.storm:storm-client to version 3.1.0, confirmed as the fix release in the Apache Storm oss-security advisory. In 3.1.0, nimbus.groups is evaluated regardless of whether nimbus.users is set. Operators must be aware of a deployment side effect: after upgrading, any cluster previously relying exclusively on nimbus.groups will begin enforcing access restrictions for the first time. This includes NimbusClient, which calls getLeader on every connection - any client whose principal is not a member of a configured group will start receiving refusals. Before deploying the upgrade, operators should enumerate all intended clients and confirm their principals belong to the configured groups. For operators who cannot upgrade immediately, the advisory-documented workaround is to also populate nimbus.users with all intended principals: a non-empty nimbus.users list restores the evaluation of nimbus.groups on affected versions. After applying either fix, operators should review historical Nimbus access logs for submitTopology, beginFileUpload, and getNimbusConf operations by principals outside the intended groups to assess whether unauthorized access occurred.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache Storm's Nimbus service enforces access control via the SimpleACLAuthorizer, which consults two configuration lists: nimbus.users (an allowlist of individual principals permitted user-level operations) and nimbus.groups (an allowlist of groups). The authorizer's user-command evaluation path contains a logic error: it checks nimbus.users first and, finding it empty, returns a blanket permit before ever evaluating nimbus.groups. This violates the intended semantics documented in docs/SECURITY.md, which presents group-only configuration as a valid and supported access-control model. The root cause is a CWE-863 (Incorrect Authorization) / CWE-670 (Always-Incorrect Control Flow Implementation) pattern - the policy check evaluates an insufficient subset of the configured policy state and short-circuits to an overpermissive result. The affected Maven artifact is org.apache.storm:storm-client versions 3.0.0 through 3.0.x. Notably, the CVE credit line states the vulnerability was discovered using Claude agents scanning open-source projects for security issues and subsequently validated by Apache Storm maintainers.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Nimbus is network-accessible (AV:N) but requires specific non-default group-only config (AC:H); valid authenticated credentials required (PR:L); full cluster operations exposed (C:H/I:H/A:H).
Primary rating from Vendor (CNA).
CVSS VectorVendor
Lifecycle Timeline
3Description PRE-NVD
Articles & Coverage 1
Executive ViewAI
Apache Storm 3.0.0's SimpleACLAuthorizer contains a critical logic flaw that silently disables group-based access control, allowing any authenticated Nimbus principal unrestricted administrative privileges including topology deployment and configuration access. Organizations that followed the documented group-only access control pattern believe their cluster is restricted when in fact every authenticated credential holds full administrative privileges, creating immediate insider threat and lateral-movement exposure.
Until a vendor-released patch is available, immediately migrate affected clusters from nimbus.groups-only to nimbus.users-based access control, implement network segmentation restricting unauthenticated access to Nimbus endpoints, or deploy an external authorization gateway (reverse proxy or API gateway) in front of Nimbus. Additionally, enable comprehensive audit logging of all topology submissions, file uploads, and configuration retrievals to detect and investigate unauthorized administrative activity by authenticated users.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-77525
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB