Loading vulnerability…
CVE-2026-33009 affects EVerest, an EV charging software stack. Versions prior to 2026.02.0 contain a race condition in handling the MQTT topic everest_external/nodered/{connector}/cmd/switch_three_phases_while_charging. The issue results in concurrent access to Charger::shared_context and internal_context without proper locking, leading to C++ undefined behavior and potential memory corruption. The flaw is remotely triggerable via MQTT and was fixed in version 2026.02.0.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
everest_external/nodered/{connector}/cmd/switch_three_phases_while_charging topic from unauthorized sources. Limit network exposure of the MQTT broker and enforce strict access controls around systems permitted to publish control messages.Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.