CVE-2026-13214
Stack buffer overflow in OCPP 1.6 client allows remote stack smash via GetConfiguration 'key'.
Is CVE-2026-13214 being exploited?
Not confirmed. CVE-2026-13214 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.51% probability of exploitation in the next 30 days.
How severe is CVE-2026-13214?
CVE-2026-13214 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-13214?
Yes. A fix has been recorded for CVE-2026-13214. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-13214 affect?
CVE-2026-13214 affects OCPP 1.6 client (subsys/net/lib/ocpp/ocpp_j.c), Zephyr-based EV charge point firmware using this OCPP client, Charge points accepting untrusted/unencrypted central system connections. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-13214?
Apply vendor firmware update; enable TLS for OCPP; restrict trusted central endpoints
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker controlling central system (or MITM on unencrypted link) can trigger stack overflow via WebSocket GetConfiguration key, causing DoS or possible remote code execution.
Immediate action required
- affected>= 4.3.0 and < 4.4.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.