Quick answers
- Is CVE-2026-82436 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82436 being exploited in the wild.
- How severe is CVE-2026-82436?
- Informational severity, published 9 November 2026.
- Which products and versions are affected?
- Apache Storm.
- Is there a fix for CVE-2026-82436?
- Yes: fixed in 3.1.0. Until then: Restrict network and credential access to the Redis state store to the cluster itself. Note that checkpoints created by affected versions may fail to restore after upgrading, requiring a migration step. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82436 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-82436?
- Check whether you run Apache Storm. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 3.1.0
Restrict network and credential access to the Redis state store to the cluster itself. Note that checkpoints created by affected versions may fail to restore after upgrading, requiring a migration step.
Technical details
DefaultStateSerializer disables Kryo class registration and uses an instantiation strategy that bypasses constructors, allowing arbitrary object deserialization from untrusted state store data. The vulnerability requires the Redis-backed state provider (non-default) and write access to the state store keyspace. Code execution occurs in the worker JVM with data-plane privileges, creating an escalation path to control-plane level compromise.
Affected products
- Apache Storm
Timeline
- 2026-11-09: disclosed