Memory corruption via off-by-one NUL write
Published Aug 31, 2026 · Updated Sep 1, 2026
Out-of-bounds write in Zephyr RTOS 3.2.0 through 4.4.1 allows remote authenticated users to corrupt memory via LwM2M JSON writes. The JSON reader's get_string() accepts a value exactly as long as the destination buffer, fills the buffer, then writes a terminating NUL one byte beyond it. Access requires the LwM2M client's authenticated server peer; the constant zero-byte write can corrupt adjacent state or crash the device.
Summary
What happened
Out-of-bounds write in Zephyr RTOS 3.2.0 through 4.4.1 allows remote authenticated users to corrupt memory via LwM2M JSON writes. The JSON reader's get_string() accepts a value exactly as long as the destination buffer, fills the buffer, then writes a terminating NUL one byte beyond it. Access requires the LwM2M client's authenticated server peer; the constant zero-byte write can corrupt adjacent state or crash the device.
The record
- CVE
- CVE-2026-14368
- Published
- Aug 31, 2026
- Updated
- Sep 1, 2026
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-787, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 31, 2026CVE publishedPublication date reported by the CVE source.
- Sep 1, 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=3.2.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.
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