Deserialization of untrusted state data in Apache Storm Client
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-502.
Summary
Apache Storm Client from 3.0.0 before 3.1.0 restores state from the state store without restricting which classes it deserializes. A party able to write to the topology's keyspace, such as a co-tenant of a shared Redis instance, can plant a serialized object graph that runs code in the worker JVM on restore (CWE-502). The flaw applies only to the Redis state provider, which is not the default.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the CNA
Description `DefaultStateSerializer`, used to persist and restore stateful bolt checkpoints, configured Kryo with class registration disabled and an instantiation strategy that constructs objects without invoking their constructors, then deserialized whatever bytes the state store returned. A party able to write to the topology's keyspace in the state store, for example a co-tenant of a shared Redis instance or anyone with network access to it, could therefore place a serialized object graph that executes code inside the worker JVM when the state is restored. This requires the Redis-backed state provider, which is not the default. Write access to a state-store key is a data-plane privilege; code execution in the worker JVM is not, so the two are not equivalent. Mitigation Upgrade to 3.1.0, where the state serializer requires registered classes. Note that this is a behaviour change for existing state: checkpoints written by an affected version may fail to restore, and a migration step may be required. Users who cannot upgrade immediately should restrict network and credential access to the state store to the cluster itself. Credit The ASF -- found using Claude agents to study the security of open-source projects, validated and reported by Apache Storm.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade Apache Storm Client to 3.1.0, where the state serializer requires registered classes. Checkpoints written by an affected version may fail to restore and may need a migration step. Until upgrading, restrict network and credential access to the state store to the cluster itself.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · CNA Apache Storm Client (Apache Software Foundation) Fixed in 3.1.0
Timeline
- 2026-11-09 Threatist record created from CVE-2026-82436
- 2026-11-09 Alias added: GHSA-g498-8632-6hwv
- 2026-11-12 CVSS score added · CISA ADP
- 2026-11-12 CISA SSVC decision points changed
- 2026-11-12 Priority changed: LOW → MEDIUM
References
More Apache vulnerabilities
- TI-2025-18529 Path equivalence in Apache Tomcat allows code execution via PUT KEVCVSS 3.1CRITICAL 10.0
- TI-2024-30292 Forced browsing in Apache OFBiz bypasses controller-view authorization KEVCVSS 3.1CRITICAL 9.8
- TI-2024-26062 Incorrect authorization in Apache OFBiz exposes screen rendering code KEVCVSS 3.1CRITICAL 9.8
- TI-2024-21190 Path traversal in Apache OFBiz leads to remote code execution KEVCVSS 3.1CRITICAL 9.8
- TI-2024-18186 Remote command execution in Apache HugeGraph-Server via Gremlin KEVCVSS 3.1CRITICAL 9.8
- TI-2023-25106 Apache ActiveMQ OpenWire deserialization allows remote code execution KEVCVSS 3.1CRITICAL 10.0
Sources
- CVE-2026-82436 · CVE Program
- CVE-2026-82436 · NVD
- FIRST EPSS
- GHSA-g498-8632-6hwv · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences