A vulnerability was identified in RT-Thread up to 5.0.2. Affected by this vulnerability is the function recvmsg in the library bsp/loongson/ls1cdev/libraries/ls1c_can.h of the component ls1c CAN Handler. Such manipulation leads to stack-based buffer overflow. Local access is required to approach this attack. The exploit is publicly available and might be used. The vendor was contacted early about this disclosure but did not respond in any way.
CVE-2026-14605
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-03. a secondary CVSS source baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 51(Track*)EG Risk 51/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity78% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 4%
- KEV
- Not listed
Published
July 3, 2026
Last Modified
July 6, 2026
Advisory Details (2)
Auto-updated Jul 3, 2026[Bug] Security-related Bug: ls1c CAN receive path trusts raw DLC and writes past rt_can_msg data · Issue #11424 · RT-Thread/rt-thread · GitHub
https://github.com/RT-Thread/rt-thread/issues/11424GitHub - RT-Thread/rt-thread: RT-Thread is an open source IoT Real-Time Operating System (RTOS). https://rt-thread.github.io/rt-thread/ · GitHub
https://github.com/RT-Thread/rt-thread/Vendor Advisories for CVE-2026-14605(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 60× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 15:50 UTCEG score recompute
- 2026-07-27 15:50 UTCGHSA enrichment
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 01:49 UTCEG score recompute
- 2026-07-27 01:49 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 12:55 UTCEG score recompute
- 2026-07-26 12:55 UTCGHSA enrichment
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 14:17 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:05 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:30 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:56 UTCGHSA enrichment
- 2026-07-16 17:02 UTCEPSS rescore
- 2026-07-16 05:00 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 16:07 UTCGHSA enrichment
- 2026-07-15 03:14 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
Show 35 moreShow fewer
- 2026-07-14 14:21 UTCGHSA enrichment
- 2026-07-14 01:28 UTCGHSA enrichment
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 12:35 UTCGHSA enrichment
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-12 23:42 UTCGHSA enrichment
- 2026-07-12 10:49 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 21:56 UTCGHSA enrichment
- 2026-07-11 09:03 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-10 20:09 UTCGHSA enrichment
- 2026-07-10 07:16 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 18:21 UTCGHSA enrichment
- 2026-07-09 05:27 UTCGHSA enrichment
- 2026-07-08 16:33 UTCGHSA enrichment
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-08 15:15 UTCEPSS rescore
- 2026-07-08 03:41 UTCGHSA enrichment
- 2026-07-07 14:47 UTCGHSA enrichment
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 01:49 UTCGHSA enrichment
- 2026-07-06 18:21 UTCNVD updateCVSS v4 → 7.1
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 15:36 UTCMITRE cvelistV5CVSS v4 → 8.5
- 2026-07-06 12:54 UTCGHSA enrichment
- 2026-07-05 23:59 UTCGHSA enrichment
- 2026-07-05 11:06 UTCGHSA enrichment
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 22:13 UTCGHSA enrichment
- 2026-07-04 09:20 UTCGHSA enrichment
- 2026-07-03 20:27 UTCEG score recompute
- 2026-07-03 20:27 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-119
- CVE-2003-0819EG 10.0EPSS p99HIGH
- CVE-2003-0903EG 10.0EPSS p98HIGH
- CVE-2003-1339EG 10.0EPSS p99HIGH
- CVE-2003-0095EG 10.0EPSS p96HIGH
- CVE-2002-2227EG 10.0HIGH
- CVE-2002-2248EG 10.0EPSS p92HIGH
- CVE-2002-2250EG 10.0EPSS p94HIGH
- CVE-2002-2251EG 10.0EPSS p93HIGH
- CVE-2002-2253EG 10.0EPSS p93HIGH
- CVE-2002-2257EG 10.0EPSS p92HIGH
Frequently asked(5)
What is CVE-2026-14605?
When was CVE-2026-14605 disclosed?
Is CVE-2026-14605 actively exploited?
What is the CVSS score of CVE-2026-14605?
How do I remediate CVE-2026-14605?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-14605
Is Your Infrastructure Affected by CVE-2026-14605?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.