CVE-2026-14606Public exploit

Memory corruption via unchecked CAN frame length

Published Jul 3, 2026 · Updated Jul 3, 2026

Stack-based buffer overflow in RT-Thread 5.0.0 through 5.0.2 allows local users to corrupt memory via a crafted CAN frame. CAN_Receive uses the frame's raw 4-bit DLC as a loop bound and copies up to 15 bytes into an eight-byte stack buffer; the driver repeats the unchecked copy into another eight-byte buffer. The path requires a Synwit SWM341 build with classic CAN enabled, which the supplied board configuration disables by default, and the published reproducer establishes memory corruption rather than reliable code execution.

CVSS severity7.8
High
EPSS probability0.20%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Stack-based buffer overflow in RT-Thread 5.0.0 through 5.0.2 allows local users to corrupt memory via a crafted CAN frame. CAN_Receive uses the frame's raw 4-bit DLC as a loop bound and copies up to 15 bytes into an eight-byte stack buffer; the driver repeats the unchecked copy into another eight-byte buffer. The path requires a Synwit SWM341 build with classic CAN enabled, which the supplied board configuration disables by default, and the published reproducer establishes memory corruption rather than reliable code execution.

The record

CVE
CVE-2026-14606
Published
Jul 3, 2026
Updated
Jul 3, 2026
Vendor
RT-Thread
Product
RT-Thread
Classifications
CWE-121, CWE-119
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 3, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 3, 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.

  1. Affected versionversion=5.0.0
  2. Affected versionversion=5.0.1
  3. Affected versionversion=5.0.2

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

RT-Thread · RT-Threadversion=5.0.0; version=5.0.1; version=5.0.2

Published CVSS scores

7.1VulDBCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
6.8VulDBAV:L/AC:L/Au:S/C:C/I:C/A:C
7.8VulDBCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-121Stack-based Buffer Overflow
CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer

Public exploit references

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