VulnerabilityPublished 9 Nov 2026

CVE-2026-82436: Apache Storm Client · Deserialization of Untrusted Data

Affects Apache Storm ClientSource CVE Database V5

Compare

Not known to be exploited : upgrade to 3.1.0 soon.

Data as of 9 Nov 2026, 10:35 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 3.1.0

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Apache Storm Client and org.apache.storm/storm-client to 3.1.0.

Affected software

Product	Affected	Fixed in
Apache Storm Clientorg.apache.storm:storm-client	Affected >=3.0.0 <3.1.0	Fixed in 3.1.0
Mavenorg.apache.storm/storm-client`pkg:maven/org.apache.storm/storm-client`Other threats	Affected >=3.0.0 <3.1.0	Fixed in 3.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Apache Storm Client to version 3.1.0 or later, where the state serializer enforces class registration during deserialization, mitigating this vulnerability. Note that upgrading may require migration of existing state checkpoints as they may fail to restore under the new serializer behavior. For users unable to upgrade immediately, restrict network and credential access to the Redis-backed state store to trusted cluster components only to prevent unauthorized write access.

Description

CVE-2026-82436 is a deserialization vulnerability in Apache Storm Client versions 3.0.0 up to but not including 3.1.0. The DefaultStateSerializer used Kryo without class registration and allowed deserialization of untrusted data from the Redis-backed state store. An attacker with write access to the state store keyspace could execute arbitrary code in the worker JVM during state restoration. This vulnerability requires the Redis-backed state provider and write access to the state store, which is a data-plane privilege. The issue is fixed in version 3.1.0, which enforces registered classes during deserialization. Users unable to upgrade immediately should restrict network and credential access to the state store.

Impact

An attacker with write access to the Redis-backed state store keyspace can execute arbitrary code within the worker JVM of Apache Storm Client versions 3.0.0 up to but not including 3.1.0. This elevates a data-plane privilege (write access to state store keys) to remote code execution in the worker process, potentially compromising the cluster's integrity and confidentiality. The vulnerability requires the Redis-backed state provider and is not exploitable via default configurations without such access.

CWE-502Deserialization of Untrusted Data (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #15OWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Architecture and Design · Implementation
If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
Implementation
When deserializing data, populate a new object rather than just deserializing. The result is that the data flows through safe input validation and that the functions are safe.
Implementation
Explicitly define a final object() to prevent deserialization.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
Software Supply Chain Security (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.2 (opens in a new tab)
V5.5.3 (opens in a new tab)
V5.5.1 (opens in a new tab)
Attack patterns
Object Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Nov 2026, 10:35 UTC

WeaknessesCWE-502

Technical details

References

Community reviews

Related threats