Skip to main content

Apache Storm CVE-2026-82431

| EUVDEUVD-2026-77525 CRITICAL
Incorrect Authorization (CWE-863)
9.8
CVSS 3.1 · Vendor
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain valid Nimbus authentication credentials
  2. Delivery
    Connect to Nimbus thrift API from any client
  3. Exploit
    SimpleACLAuthorizer finds nimbus.users empty and returns early
  4. Execution
    Group restriction check in nimbus.groups is never evaluated
  5. Persist
    Attacker receives full user-level authorization
  6. Impact
    Submit 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) org.apache.storm:storm-client version 3.0.0 through 3.0.x deployed with an active Nimbus instance; (2) the operator has configured nimbus.groups with at least one group entry intending to restrict cluster access, while nimbus.users is explicitly empty or unset; (3) the attacker holds valid Nimbus authentication credentials for any recognized principal regardless of group membership. The vulnerability does NOT affect deployments where nimbus.users is also populated (even partially), since a non-empty nimbus.users list causes group evaluation to proceed normally. The shipped default - both lists empty, meaning no access restriction - is also unaffected and unchanged. The bypass is entirely silent: no log line, configuration warning, or runtime indicator reveals that group restrictions are being ignored, preventing self-detection without reading this advisory.

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 nimbus.groups while leaving nimbus.users unset - a non-default but explicitly documented configuration. Default deployments (both lists empty, meaning no restriction) are unaffected. For vulnerable deployments the impact is severe: full user-level Nimbus operations are exposed, including topology submission, blob store file upload, and configuration retrieval, which together constitute effective cluster takeover capability. The silent failure mode (no log entries, no configuration warning) amplifies risk because affected operators cannot detect the misconfiguration without reading this advisory. The absence of any KEV listing and no public POC reduces immediate threat from opportunistic actors, but insider threat or compromised credentials within an organization relying solely on group-based restriction represent a realistic concern. CVSS interpretation: AV:N (Nimbus is a network thrift service), AC:H (requires specific non-default operator configuration), PR:L (valid authentication credentials required), S:U, C:H/I:H/A:H (full cluster operations).

Exploit ScenarioDerived

An authenticated Nimbus user whose principal is not a member of any configured group connects to the cluster thrift API. Because SimpleACLAuthorizer returns a blanket permit when nimbus.users is empty, the user is granted full user-level access and submits a resource-exhausting or malicious topology, uploads rogue jars to the blob store, or calls getNimbusConf to extract cluster credentials or configuration. No public exploit code is available at time of analysis; exploitation requires valid credentials and knowledge of the configuration gap.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Apache Storm Client 3.0.0 <3.1.0

Affected Packages

euvd apache_storm_client fix: 3.1.0

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

Vendor (CNA) PRIMARY 9.8 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.5 HIGH

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

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (CNA).

CVSS VectorVendor

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
CVSS changed
Sep 14, 2026 - 20:22 NVD
9.8 (CRITICAL)
Patch available
Sep 14, 2026 - 16:02 EUVD
CVE Published
Sep 13, 2026 - 14:28 oss-security
CRITICAL

Description PRE-NVD

Disclosed via oss-security. NVD scoring and full description are pending.

Executive ViewAI

Why It Matters

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.

Business Impact: High
Compensating Controls

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

EPSS Score
0.5%
Top 60% exploitable
Prevalence
Low
niche stream processor, largely displaced by Flink and Kafka Streams
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.5%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Total

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy