What is CVE-2026-82434?

CVE-2026-82434 is Apache Storm Nimbus, Apache Storm Client: Disclosure of the Topology ZooKeeper Credential to Read-Only Users and to Logs. The supplied enrichment data classifies it as Credentials mapped to CWE-522 CWE-522; CWE-532 CWE-532.

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-82434. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-82434 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-82434. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS 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-82434 using CVSS 10, 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.

criticalCredentials

CVE-2026-82434

CVE-2026-82434 — Apache Storm Nimbus, Apache Storm Client: Disclosure of the Topology ZooKeeper Credential to Read-Only Users and to Logs

Description When ZooKeeper authentication is configured, Storm deliberately retains `storm.zookeeper.topology.auth.payload` in the topology configuration, because workers need it. Nimbus then served that configuration verbatim to any caller holding read-only topology permissions, so a user whose only grant was the ability to view a topology received its ZooKeeper credential. That credential is not read-only. The cluster state implementation uses write-capable ACLs for worker heartbeats, backpressure and error state, so a recipient can forge or remove that state for the topology concerned. It is not a write credential on assignments. The same advisory covers the submission client, which logged the generated payload at INFO on every submission that generated one, and the SASL handlers, which logged it at DEBUG. The credential therefore also reached any log aggregation or support bundle collected from the cluster. Mitigation Upgrade to 3.1.0, where the payload is removed from the configuration served to read-only callers and is no longer written to logs. Users who cannot upgrade immediately should rotate `storm.zookeeper.topology.auth.payload` for existing topologies, review retained logs and support bundles for the value, and restrict read-only topology permissions to trusted principals. 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

critical

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 Client	3.0.0 to < 3.1.0	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
10	CVSS 4.0	critical	—	—	Apache Software Foundation (CNA)

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

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-532 · Insertion of Sensitive Information into Log File

Read Application Data

Mitigation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.

Weakness & attack patterns

CWE-522
CWE-532

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.

Prioritize edge telemetry for network-reachable Apache Storm Nimbus, Apache Storm Client.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

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

2026
Added · CVSS 3.1 10.0 (AV:N)
Sep 14, 2026 · NVD
Initial · CVE published
Sep 14, 2026 · NVD
Added · GHSA-6fmw-8rj9-p9pg published (critical)
Sep 14, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 14, 2026 · SOCRadar CTI

References

5 on the record

lists.apache.org/thread/1t7hggrz59rdq792qm1pnkqj0ogm2szq
Vendor Advisory
www.openwall.com/lists/oss-security/2026/09/13/14
Vendor Advisory
www.openwall.com/lists/oss-security/2026/09/13/23
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-82434
NVD
github.com/advisories/GHSA-6fmw-8rj9-p9pg
Exploit, Third Party Advisory

Coverage

3 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-82434 is Apache Storm Nimbus, Apache Storm Client: Disclosure of the Topology ZooKeeper Credential to Read-Only Users and to Logs, a critical vulnerability affecting Apache Storm Nimbus, Apache Storm Client 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-82434. Public exploit evidence is: A public PoC is not confirmed from current sources for CVE-2026-82434. 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 10 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.