CVE-2026-125709 · Runtime
NO FIX YET
When a byte-by-byte write to a file stream fails, libstdc++ may still append the data to its internal buffer. An attacker who can force repeated write failures in an affected service can trigger a buffer overflow, leading to denial of service or memory corruption.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Services built with libstdc++ that write to file streams and can be made to hit repeated write failures, for example when disk space runs out or a file descriptor is closed. Programs that do not write through file streams, or that cannot be driven into repeated write failures, are less exposed. The sources do not list affected versions.
Not affected if no-file-stream-writes
Who cares c++, gcc, libstdc++
Unknown from the sources.
No fix yet, per the sources.
A flaw was found in libstdc++. When a byte-by-byte write operation fails during file stream processing, the library may still append data into the internal memory buffer. An attacker capable of inducing repeated write failures in an affected service can trigger a buffer overflow, potentially resulting in a Denial of Service (DoS) or memory corruption.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.