Reader-thread crash via unbounded GetConfiguration key copy
Published Aug 25, 2026 · Updated Aug 25, 2026
Stack buffer overflow in Zephyr RTOS 4.3.0 through 4.4.1 allows remote attackers to crash the OCPP reader thread via a crafted request. The GetConfiguration parser copies the request's JSON key with unbounded strcpy into a fixed 50-byte stack buffer. Reachability requires the OCPP library and control of the configured central system, or interception of an unencrypted WebSocket; the grounded consequence is a reader-thread crash.
Summary
What happened
Stack buffer overflow in Zephyr RTOS 4.3.0 through 4.4.1 allows remote attackers to crash the OCPP reader thread via a crafted request. The GetConfiguration parser copies the request's JSON key with unbounded strcpy into a fixed 50-byte stack buffer. Reachability requires the OCPP library and control of the configured central system, or interception of an unencrypted WebSocket; the grounded consequence is a reader-thread crash.
The record
- CVE
- CVE-2026-13214
- Published
- Aug 25, 2026
- Updated
- Aug 25, 2026
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.3.0 <4.4.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo