CVE-2026-14606
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA security flaw has been discovered in RT-Thread up to 5.0.2. Affected by this issue is the function CAN_Receive in the library bsp/synwit/libraries/SWM341_CSL/CMSIS/DeviceSupport/SWM341.h of the component SWM341 CAN Handler. Performing a manipulation results in stack-based buffer overflow. The attack needs to be approached locally. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceStack-based buffer overflow in RT-Thread's CAN_Receive function within the SWM341 CAN driver (bsp/synwit/libraries/SWM341_CSL/CMSIS/DeviceSupport/SWM341.h). The vulnerability allows a local attacker to overflow a stack-allocated buffer, potentially achieving code execution or causing denial of service. This affects all RT-Thread versions up to 5.0.2.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check RT-Thread versionLocate the RT-Thread version definition in your codebase (commonly in version.h, rtconfig.h, or the root CMakeLists.txt/Kconfig file) and compare it to the affected range. Versions 5.0.2 and below are affected.Affected if The installed RT-Thread version is 5.0.2 or any earlier version (e.g., 5.0.1, 4.1.0, etc.)
-
Verify SWM341 BSP is in useSearch your project for references to the SWM341 board support package - look for directories or files containing 'SWM341' or 'synwit' in the bsp/ folder of your RT-Thread project.Affected if The project includes the bsp/synwit/SWM341 directory or references to the SWM341 chip family.
-
Confirm CAN driver is enabledCheck your RT-Thread configuration (rtconfig.h or Kconfig) for CAN-related settings such as RT_USING_CAN or BSP_USING_CAN, and verify the CAN driver source files are compiled into your build.Affected if CAN support is enabled in the RT-Thread configuration and the CAN driver is part of the built firmware.
-
Inspect the vulnerable CAN_Receive functionLocate the file bsp/synwit/libraries/SWM341_CSL/CMSIS/DeviceSupport/SWM341.h in your RT-Thread installation and examine the CAN_Receive function implementation for missing or insufficient bounds checking on received message lengths.Affected if The SWM341.h file contains the CAN_Receive function and lacks proper length validation before copying data into stack buffers.
You are affected if your RT-Thread version is 5.0.2 or earlier AND you are using the SWM341 CAN driver with CAN functionality enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict bounds checking in the CAN_Receive function to validate incoming CAN message lengths against buffer allocations; consider updating to any newer RT-Thread release if available, or apply vendor-supplied patches for the SWM341 driver.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-14606 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-14606 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data