CVE-2026-10848 is a memory-safety bug in the experimental OCPP 1.6 client of Zephyr RTOS: an OCPP central system, or an attacker on a plain ws:// link, can send an RPC frame whose uid or action field is 127 bytes or longer, which the parser copies without a terminator and then reads past a 128-byte stack buffer. NVD scores it 8.6.
Vulnerability summary
CVSS base score
8.6
High severity
EPSS score (FIRST)
0.4%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2026-10848 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| Zephyr RTOS (OCPP 1.6 client, subsys/net/lib/ocpp, CONFIG_OCPP) | cpe:2.3:o:zephyrproject:zephyr:*:*:*:*:*:*:*:* | 4.3.0 to before 4.5.0 (NVD CPE); patched in 4.4.2 (Zephyr GHSA-jgqq-7mjj-w642) |
What does this mean for affected devices?
Where is the bug in Zephyr's OCPP client?
NVD's description places it in parse_rpc_msg() in subsys/net/lib/ocpp/ocpp_j.c, where the helper extract_string_field() copied the uid and action fields "with strncpy(out_buf, token + 1, outlen - 1) and then scanned the result with strchr(out_buf, '"')". Because strncpy leaves no NUL when the source is 127 bytes or longer, the scan "reads past the 128-byte destination buffer into adjacent stack memory", and a stray quote byte beyond the buffer causes "a one-byte out-of-bounds NUL write" (NVD). The feature is marked experimental and only built when CONFIG_OCPP is enabled.
How severe is it?
NVD's Primary CVSS 3.1 score is 8.6, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H, with CWE-125, out-of-bounds read. Zephyr, as CNA, scores it 7.0 with high attack complexity and lists CWE-125 and CWE-787. The two primary sources differ on disclosure: NVD's text says "the over-read data is not reflected to the peer", while Zephyr's advisory GHSA-jgqq-7mjj-w642 argues the unterminated uid is reused with %s in frame_rpc_call_res() and can become "network-visible to the attacker as reflected stack data". Both agree that a remotely triggered denial of service of the charge point is the main impact.
Which Zephyr versions carry the fix?
The GHSA lists Zephyr 4.3.0 up to 4.4.2 as vulnerable and 4.4.2 as patched. NVD's CPE marks 4.3.0 to before 4.5.0. The fix on main, commit e500f7b of 2026-06-03, replaces the hand-written parser with json_mixed_arr_parse() and is contained in the v4.5.0 tag.
Why does this matter for EV chargers?
Zephyr's OCPP client runs in charge-point firmware and parses whatever the CSMS sends. Our OCPP protocol security guide lists this CVE with its sibling Zephyr OCPP flaws and recommends fuzzing the station's OCPP parser. Zephyr's description itself notes "OCPP is commonly deployed over plain ws://", which turns any on-path attacker into a sender. Other Zephyr network-parser bugs in our corpus include the DNS name parser write, CVE-2026-1678.
Is it in KEV, and what is the EPSS score?
It is not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). FIRST EPSS gives it 0.00376, the 32.1st percentile, in the 2026-11-16 dataset (CISA KEV, FIRST EPSS).
What should firmware teams do?
Check whether the shipped build sets CONFIG_OCPP; if it does, move to Zephyr 4.4.2 or 4.5.0 and rebuild, and connect only over TLS to a CSMS you control. A build without CONFIG_OCPP can carry a not-affected statement with the configuration as evidence. Our memory corruption fix guide covers bounded string handling.
Evidence
- extract_string_field() in parse_rpc_msg() uses strncpy without NUL termination and strchr reads past the 128-byte stack buffer; possible one-byte OOB NUL write; feature EXPERIMENTAL behind CONFIG_OCPP. — NVD
- NVD Primary CVSS 3.1 8.6 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H), CWE-125; Zephyr CNA 7.0; CPE 4.3.0 to before 4.5.0. — NVD
- GHSA-jgqq-7mjj-w642 (high), published 2026-08-02: vulnerable >= 4.3.0, < 4.4.2; patched 4.4.2; uid reused in frame_rpc_call_res() with %s. — Zephyr Project security advisory
- Fix commit e500f7b (2026-06-03) replaces manual parsing with JSON mixed-array support; contained in tag v4.5.0. — Zephyr Project GitHub
- Not in the CISA KEV catalog as of 2026-11-16 (catalog version 2026.11.13). — CISA KEV
- EPSS 0.00376 (32.1st percentile) in the 2026-11-16 dataset. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Is every Zephyr-based device affected by CVE-2026-10848?
No. The OCPP 1.6 client is an experimental subsystem that is only compiled when CONFIG_OCPP is enabled, so only firmware built with Zephyr's OCPP library (typically charge-point firmware) in an affected version carries the bug.
Who can send the malicious frame?
The OCPP central system the charger connects to, if it is malicious or compromised, or an on-path attacker when OCPP runs over plain ws://. NVD's description names both.
Which version fixes it?
Zephyr's advisory GHSA-jgqq-7mjj-w642 lists 4.4.2 as the patched release. NVD's CPE range marks 4.3.0 up to, but not including, 4.5.0, and the fix commit e500f7b is part of the v4.5.0 tag.
Does it leak memory to the attacker?
The sources differ. NVD's text says the over-read data is not reflected to the peer, while Zephyr's GHSA describes the unterminated uid being reused in the CALLRESULT reply and becoming network-visible. Both describe a remotely triggered denial of service.
Questions about this page?