CVE-2026-14368
MEDIUMDescription
The LwM2M JSON content formatter's get_string() in subsys/net/lib/lwm2m/lwm2m_rw_json.c copies a parsed JSON string into a caller-supplied buffer and NUL-terminates it. The length guard used if (string_length > buflen), which accepts a string whose length is exactly buflen. After memcpy() fills the whole buffer, buf[string_length] = '\0' then writes one byte past the end of the buffer (CWE-787). The string value and its length are taken directly from the incoming CoAP payload during a LwM2M WRITE: do_write_op_json() parses the payload obtained from coap_packet_get_payload(), and get_string() is invoked from lwm2m_write_handler() (engine_get_string() in subsys/net/lib/lwm2m/lwm2m_message_handling.c) for a LWM2M_RES_TYPE_STRING resource. The destination buf/buflen is either the resource instance's fixed data buffer (res_inst->data_ptr/max_data_len) or the engine validation buffer (msg->ctx->validate_buf). A LwM2M server (the client's DTLS peer) can therefore write a string resource with a value whose length equals the target buffer size and force a one-byte overflow. The overflow is a single out-of-bounds write of the constant byte 0x00 immediately past the resource or validation buffer, corrupting the adjacent byte in memory. It is not an information leak and the written value is fixed, so it is not a direct code-execution primitive, but it can corrupt adjacent state (an adjacent resource value, a length/flag field, or a struct field) and cause data corruption or a crash. Triggering the write is deterministic; the resulting impact depends on memory layout. The fix changes the guard to string_length >= buflen, rejecting the exact-length case and aligning the JSON formatter with the other content formatters (lwm2m_rw_plain_text.c, lwm2m_rw_oma_tlv.c, lwm2m_rw_senml_json.c, lwm2m_rw_cbor.c, lwm2m_rw_senml_cbor.c), which already used the correct boundary check.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 14% of all known CVEs.
References
Related Vulnerabilities
Other CWE-193 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2021-3156 | High | 7.8 | 100% | KEV | Fix |
| CVE-2003-0466 | Critical | 9.8 | 78% | - | - |
| CVE-2023-44444 | High | 7.8 | 56% | - | Fix |
| CVE-2021-23017 | High | 7.7 | 53% | - | Fix |
| CVE-2023-28709 | High | 7.5 | 48% | - | Fix |
| CVE-2018-8828 | Critical | 9.8 | 30% | - | Fix |
Common questions
How do I fix CVE-2026-14368?
No published fix for CVE-2026-14368 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-14368 being actively exploited?
Not that we know of. CVE-2026-14368 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.23% is the estimated probability that it will be exploited in the next 30 days. That is higher than 14% of all scored CVEs.
How severe is CVE-2026-14368?
CVE-2026-14368 has a CVSS v3 base score of 5.4, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-14368
Markdown
[](https://tridentstack.com/cve/CVE-2026-14368)HTML
<a href="https://tridentstack.com/cve/CVE-2026-14368"><img src="https://tridentstack.com/cve/badge/CVE-2026-14368.svg" alt="CVE-2026-14368"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-01.