Description
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: 2026-09-14
Score: 10 Critical
EPSS: < 1% Very Low
KEV: No
Impact: Credential Exposure with Potential Integrity Impact
Action: Patch Immediately
AI Analysis

Impact

Apache Storm Nimbus and Client have a flaw where the Zookeeper topology authentication payload is included in the topology configuration that is accessible to users with only read‑only topology permissions. The exposed credential is not read‑only; it grants write‑capable ACLs for worker heartbeats, backpressure and error state. An attacker who obtains the payload can forge or delete state for the affected topology, effectively tampering with cluster operation and potentially disrupting service. This constitutes a serious breach of confidentiality, integrity, and availability for any Storm deployment that authenticates to Zookeeper.

Affected Systems

The vulnerability affects Apache Storm Client and Nimbus. No specific product versions are listed, but the advisory specifies that upgrading to version 3.1.0 removes the problematic payload from served configurations and stops logging the credential. Operations running any earlier Storm release are susceptible until a patch or mitigated configuration is applied.

Risk and Exploitability

With a CVSS score of 10, the exploitation risk is high. The EPSS score is not available, and the vulnerability is not yet listed in CISA’s KEV catalogue, suggesting that it may not yet be widely exploited publicly, yet the nature of the credential leak makes it attractive for malicious actors. Attackers can retrieve the payload by querying topology metadata or by accessing any log output where the payload was written, so the attack vector is likely remote through authenticated API calls or log aggregation systems. Once the credential is in hand, the attacker can modify cluster state via write‑capable Zookeeper ACLs, undermining topology integrity and availability.

Generated by OpenCVE AI on September 15, 2026 at 13:41 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Storm to version 3.1.0 or newer where the topology authentication payload is removed from configuration served to read‑only users and is no longer persisted in logs.
  • If an upgrade cannot be performed immediately, rotate the storm.z any exposed credentials unusable.
  • Review and delete any logs or support bundles that captured the credential, and restrict read‑only topology permissions to trusted principals only.

Generated by OpenCVE AI on September 15, 2026 at 13:41 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 14 Sep 2026 21:00:00 +0000

Type Values Removed Values Added
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 14 Sep 2026 14:30:00 +0000

Type Values Removed Values Added
Description 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.
Title Apache Storm Nimbus, Apache Storm Client: Disclosure of the Topology ZooKeeper Credential to Read-Only Users and to Logs
Weaknesses CWE-522
CWE-532
References
Metrics cvssV4_0

{'score': 10, 'vector': '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'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: apache

Published:

Updated: 2026-09-14T19:50:34.074Z

Reserved: 2026-08-29T10:28:41.032Z

Link: CVE-2026-82434

cve-icon Vulnrichment

Updated: 2026-09-14T14:13:34.520Z

cve-icon NVD

Status : Deferred

Published: 2026-09-14T15:17:10.453

Modified: 2026-09-14T20:58:48.430

Link: CVE-2026-82434

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-15T13:45:07Z

Weaknesses
  • CWE-522

    Insufficiently Protected Credentials

  • CWE-532

    Insertion of Sensitive Information into Log File