Board memory corruption via unchecked floating-point precision
Published Jan 21, 2026 · Updated Jan 21, 2026
Stack buffer overflow in Arduino AVR Boards before 1.8.7 allows local users to corrupt memory through high-precision conversion. The WString float and double constructors pass caller-controlled decimalPlaces values to dtostrf, which writes past fixed-size stack buffers. Reaching the flaw requires locally executing firmware that supplies excessive precision; denial of service results directly, while code execution requires additional unspecified conditions.
Summary
What happened
Stack buffer overflow in Arduino AVR Boards before 1.8.7 allows local users to corrupt memory through high-precision conversion. The WString float and double constructors pass caller-controlled decimalPlaces values to dtostrf, which writes past fixed-size stack buffers. Reaching the flaw requires locally executing firmware that supplies excessive precision; denial of service results directly, while code execution requires additional unspecified conditions.
The record
- CVE
- CVE-2025-69209
- Published
- Jan 21, 2026
- Updated
- Jan 21, 2026
- Vendor
- Arduino
- Product
- Arduino AVR Boards
- Classifications
- CWE-120, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 21, 2026CVE publishedPublication date reported by the CVE source.
- Jan 21, 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=< 1.8.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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