
🔓 CVE-2026-82436 turns write access to Storm's Redis state store into code execution in the worker JVM. 📌 What happened: In Apache Storm Client 3.0.0 before 3.1.0, DefaultStateSerializer deserializes Redis-backed state without class registration, an unsafe Kryo deserialization flaw. 🔑 Key facts: ▪️ Vendor severity: Important; no CVSS score yet ▪️ Attacker writes a malicious object graph into the keyspace ▪️ Code runs when the worker restores that checkpoint ▪️ Fixed in 3.1.0; no known exploitation, PoC or KEV listing ⚠️ Why it matters: Anyone who can write to the topology's Redis keyspace can run code inside Storm workers. 🛡️ Do this now: 1⃣ Upgrade to Apache Storm 3.1.0 2⃣ Restrict Redis state-store access to the Storm cluster 3⃣ Keep that Redis away from untrusted tenants and segment it 4⃣ Monitor Redis logs for unexpected writes to Storm keyspaces 🔗 Full analysis: https://badgersignal.com/articles/cve-2026-82436-apache-storm-client-deserialization-of-untrusted-data-remote-code-execution 📊 Infographic attached for the breakdown at a glance. 💬 Which services besides Storm hold write credentials to your topology state store in Redis? #CyberSecurity #ThreatIntelligence #InfoSec #BadgerSignal #ApacheStorm #Redis
Post summary
The text discloses CVE-2026-82436, an unsafe deserialization flaw in Apache Storm Client 3.0.0 fixed in version 3.1.0, providing technical root cause details and explicit upgrade/workaround instructions while noting no known exploitation or public PoC exists.

