CVE-2026-82436 · Package
NO FIX YET · SEE WHAT TO DO
Apache Storm's bolt state serializer deserializes whatever bytes the state store returns, with Kryo class registration disabled. A party who can write to the topology's keys in the state store, such as a co-tenant of a shared Redis, can make code run inside the worker JVM when state is restored.
first public Nov 9, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Only topologies that use the Redis-backed state provider are exposed, since it is not the default. The risk comes from anyone who can write to the state-store keys, such as a co-tenant on a shared Redis or anyone with network access to it. Teams with Redis restricted to the cluster and tight credentials on the state store are lower risk, though upgrading is still the stated fix.
Not affected if default-state-provider, isolated-state-store, no-redis-state-store
Who cares apache-storm, jvm, redis, stateful-bolts
3.1.0, per the mitigation text.3.1.0, where the state serializer requires registered classes. Note that checkpoints written by affected versions may fail to restore and a migration step may be required.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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.