CVE-2025-69209 ArduinoCore-avr has Stack-Based Buffer Overflow in WString Float/Double Constructors

Medium 6.9 Published Updated

Attacker can trigger stack buffer overflow via high-precision float conversion, potentially enabling code execution or denial of service on Arduino AVR boards.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2025-69209?

CVE-2025-69209 is a medium-severity memory corruption vulnerability in ArduinoCore-avr, published on 21 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

ArduinoCore-avr contains the source code and configuration files of the Arduino AVR Boards platform. A vulnerability in versions prior to 1.8.7 allows an attacker to trigger a stack-based buffer overflow when converting floating-point values to strings with high precision. By passing very large `decimalPlaces` values to the affected String constructors or concat methods, the `dtostrf` function writes beyond fixed-size stack buffers, causing memory corruption and denial of service. Under specific conditions, this could enable arbitrary code execution on AVR-based Arduino boards.

### Patches

- The Fix is included starting from the `1.8.7` release available from the following link [ArduinoCore-avr v1.8.7](https://github.com/arduino/ArduinoCore-avr)

- The Fixing Commit is available at the following link [1a6a417f89c8901dad646efce74ae9d3ddebfd59](https://github.com/arduino/ArduinoCore-avr/pull/613/commits/1a6a417f89c8901dad646efce74ae9d3ddebfd59)

### References

- [ASEC-26-001 ArduinoCore-avr vXXXX Resolves Buffer Overflow Vulnerability](https://support.arduino.cc/hc/en-us/articles/XXXXX)

### Credits

- Maxime Rossi Bellom and Ramtine Tofighi Shirazi from SecMate (https://secmate.dev/)

Weakness: CWE-120

Which versions are affected by CVE-2025-69209?

How do I fix CVE-2025-69209?

Upgrade to a fixed version.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2025-69209 being exploited?

There is no known exploitation of CVE-2025-69209 in the wild and no public exploit code.

Sources

Also known as DEBIAN-CVE-2025-69209, GHSA-pvx3-fm7w-6hjm, UBUNTU-CVE-2025-69209.

Is CVE-2025-69209 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free