CVE-2026-26399 | stm32duino Arduino_Core_STM32 up to 1.6.x pwm_start memory corruption
VulDBArchived Apr 20, 2026✓ Full text saved
A vulnerability categorized as critical has been discovered in stm32duino Arduino_Core_STM32 up to 1.6.x . This affects the function pwm_start . The manipulation results in memory corruption. This vulnerability was named CVE-2026-26399 . The attack needs to be approached within the local network. There is no available exploit. It is advisable to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-358339 · CVE-2026-26399 · EUVD-2026-23912
STM32DUINO ARDUINO_CORE_STM32 UP TO 1.6.X PWM_START MEMORY CORRUPTION
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
7.6 $0-$5k 4.08
Summaryinfo
A vulnerability identified as critical has been detected in stm32duino Arduino_Core_STM32 up to 1.6.x. This vulnerability affects the function pwm_start. This manipulation causes memory corruption. The identification of this vulnerability is CVE-2026-26399. There is no exploit available. You should upgrade the affected component.
Detailsinfo
A vulnerability has been found in stm32duino Arduino_Core_STM32 up to 1.6.x and classified as critical. Affected by this vulnerability is the function pwm_start. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
A stack-use-after-return issue exists in the Arduino_Core_STM32 library prior to version 1.7.0. The pwm_start() function allocates a TIM_HandleTypeDef structure on the stack and passes its address to HAL initialization routines, where it is stored in a global timer handle registry. After the function returns, interrupt service routines may dereference this dangling pointer, resulting in memory corruption.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-26399 since 02/16/2026. The exploitation appears to be easy. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 1.7.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-23912).
Productinfo
Vendor
stm32duino
Name
Arduino_Core_STM32
Version
1.0
1.1
1.2
1.3
1.4
1.5
1.6
Website
Product: https://github.com/stm32duino/Arduino_Core_STM32/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.6
VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Memory corruption
CWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: Arduino_Core_STM32 1.7.0
Timelineinfo
02/16/2026 CVE reserved
04/20/2026 +62 days Advisory disclosed
04/20/2026 +0 days VulDB entry created
04/20/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: github.com
Status: Confirmed
CVE: CVE-2026-26399 (🔒)
GCVE (CVE): GCVE-0-2026-26399
GCVE (VulDB): GCVE-100-358339
EUVD: 🔒
Entryinfo
Created: 04/20/2026 19:58
Updated: 04/20/2026 23:33
Changes: 04/20/2026 19:58 (55), 04/20/2026 23:33 (1)
Complete: 🔍
Cache ID: 99:E45:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸