CVE-2026-82433Not yet in NVD's feed. The description, CVSS and CWE below come from the CVE Numbering Authority's own record, not from NVD analyst review. NVD's own page for this identifier may not exist yet.
Published yesterday. NVD backfills CPE data for days or weeks after publication, and OSV and the exploit indexes lag too. Scope and status here may change.
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.
CWE-522CWE-862 · Missing authorization
No public exploit
Nothing published shows this CVE being exploited, which is not the same as ruling it out.
CVSS E:U
In RASP's scope, but nothing published names a fix and nothing published shows an exploit. Neither of the two things VRT can act on exists, which is a claim about the available evidence, not about the vulnerability.
| Decided by | no-exploit : With no fix path, a public exploit, or a CISA record of one |
|---|---|
| Finding | Resolved from QUEUED-FOR-REVIEW: this CVE affects a known product, but nothing published names a fix and nothing published shows an exploit. That is a statement about the evidence, not about the defect — it does not mean the vulnerability is unimportant or unreachable, only that neither of the two things VRT can act on exists. |
| URL | Tags |
|---|---|
| https://lists.apache.org/thread/ohw4s30rhm2r20498c0zbqxyy7xd5hxl | vendor-advisory |
| Published | 2026-09-14 | By the CVE Program. |
|---|---|---|
| NVD record modified | 2026-09-14 | NVD's own last-modified date for this record. |