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

> Attackers can retrieve unredacted daemon configuration including sensitive credentials via Nimbus and UI endpoints due to missing authorization checks and masking.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-3p33-32v8-fg8j

## What is CVE-2026-82433?

CVE-2026-82433 is a medium-severity vulnerability in Apache Storm Nimbus, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization), CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2026-82433?


## How do I fix CVE-2026-82433?

No fix has been published for CVE-2026-82433 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82433 being exploited?

There is no known exploitation of CVE-2026-82433 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82433 and fix it if it is affected.

What it is: CVE-2026-82433 is a medium-severity vulnerability in Apache Storm Nimbus, published on 14 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-82433 in the wild and no public exploit code.

Affected product: Apache Storm Nimbus. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82433/ (Markdown: https://insights.sbomify.com/CVE-2026-82433/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82433
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82433
- OSV: https://osv.dev/vulnerability/CVE-2026-82433

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82433/
Summaries are generated and may contain mistakes; the official description above is the record.