What is CVE-2026-82433?

CVE-2026-82433 is Apache Storm Nimbus, Apache Storm UI: Disclosure of Unredacted Daemon Configuration via Nimbus and the UI. The supplied enrichment data classifies it as Credentials mapped to CWE-522 CWE-522; CWE-862 CWE-862.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-82433. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-82433 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

A public PoC is not confirmed from current sources for CVE-2026-82433. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with Not reported where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-82433 using CVSS null, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

Credentials

CVE-2026-82433

CVE-2026-82433 — Apache Storm Nimbus, Apache Storm UI: Disclosure of Unredacted Daemon Configuration via Nimbus and the UI

Description `getNimbusConf` returned the complete daemon configuration without redaction after only a user-level authorization check. Where the cluster is configured with them, that response includes `storm.zookeeper.auth.payload` and the keystore and truststore passwords for the Thrift, Netty and ZooKeeper TLS configuration. The project masks passwords elsewhere before display, so the omission here is inconsistent rather than intended. The UI endpoint `/api/v1/cluster/configuration` compounded this. It carried no `@AuthNimbusOp` annotation, and the authorization filter treated a missing annotation as "no gate required" and returned immediately, so the endpoint applied no per-user check at all and proxied the request under the UI daemon's own principal. Any user able to pass `ui.filter` therefore received the full configuration, including principals that Nimbus itself would have refused. Mitigation Upgrade to 3.1.0, where credential-bearing values are masked before the configuration is served and where every UI API endpoint must declare its authorization explicitly. Users who cannot upgrade immediately should place the UI behind an authenticating reverse proxy that restricts `/api/v1/cluster/configuration`, and should rotate the ZooKeeper authentication payload and any TLS keystore or truststore passwords that were reachable through it. Credit The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.

Published Sep 14, 2026Updated Sep 14, 2026Sources: NVD, Apache Software Foundation (CNA), GitHub, GitHub Security Advisory, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

ahead of 0% of scored CVEs

Affects

Apache

2 products listed

CVSS base

Unscored

no source published a base score

Remediation

The vendor's own words where we have them.

Upgrade Apache Storm Nimbus to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Apache	Apache Storm Nimbus	3.0.0 to < 3.1.0	Vulnerable
Apache	Apache Storm UI	3.0.0 to < 3.1.0	Vulnerable

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-522 · Insufficiently Protected Credentials

Gain Privileges or Assume Identity

Mitigation: Use an appropriate security mechanism to protect the credentials.

CWE-862 · Missing Authorization

Read Application Data
Read Files or Directories
Modify Application Data
Modify Files or Directories

Mitigation: Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.

Weakness & attack patterns

CWE-522
CWE-862

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-102 · Session SidejackingCAPEC-474 · Signature Spoofing by Key TheftCAPEC-50 · Password Recovery ExploitationCAPEC-509 · KerberoastingCAPEC-551 · Modify Existing ServiceCAPEC-555 · Remote Services with Stolen CredentialsCAPEC-560 · Use of Known Domain CredentialsCAPEC-561 · Windows Admin Shares with Stolen CredentialsCAPEC-600 · Credential StuffingCAPEC-644 · Use of Captured Hashes (Pass The Hash)CAPEC-645 · Use of Captured Tickets (Pass The Ticket)CAPEC-652 · Use of Known Kerberos Credentials

T1552.004Unsecured Credentials: Private Keys
T1558.003Steal or Forge Kerberos Tickets: Kerberoasting
T1543Create or Modify System Process

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /api/v1/cluster/configuration.

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Initial · CVE published
Sep 14, 2026 · NVD
Added · GHSA-3p33-32v8-fg8j published (unknown)
Sep 14, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 14, 2026 · SOCRadar CTI

References

4 on the record

lists.apache.org/thread/ohw4s30rhm2r20498c0zbqxyy7xd5hxl
Vendor Advisory
www.openwall.com/lists/oss-security/2026/09/13/13
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-82433
NVD
github.com/advisories/GHSA-3p33-32v8-fg8j
Exploit, Third Party Advisory

Coverage

2 stories from the feeds we poll

Elsewhere on this site

Apacheevery CVE for this vendor
Credentialssame class
CWE-522other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-82433 is Apache Storm Nimbus, Apache Storm UI: Disclosure of Unredacted Daemon Configuration via Nimbus and the UI, a unscored vulnerability affecting Apache Storm Nimbus, Apache Storm UI from Apache Software Foundation. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-82433. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-82433. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS null describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.