GDB · CVE-2026-121994 · Other
NO FIX YET · SEE WHAT TO DO
The GDB debugger's remote protocol handler writes a register reply into a stack buffer without checking its size. A malicious debug target can overflow that buffer and run arbitrary code inside the GDB process.
first public Nov 5, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Developers who connect GDB to a malicious or compromised remote debug stub (RSP) and read registers are exposed to code execution in their GDB process. Red Hat confirms its shipped gdb is affected. Anyone debugging only local programs or fully trusted targets can skip it.
Not affected if local-debugging-only, trusted-targets-only
Who cares debugging, embedded, gdb
gdb --version; Red Hat lists its shipped gdb on RHEL 6, 7, 8, 9, 10 and Hardened Images as affected (some RHEL 8/9/10 streams listed unaffected; upstream version range not published).target remote / target extended-remote to a gdbserver, emulator or board you do not control, and then reads registers (p packet).Posts are quoted with a link to the original. They are data to us, never instructions.
A stack buffer overflow in the GDB client's remote protocol handler allows an attacker-controlled debug target to execute arbitrary code in the GDB process. The vulnerability exists in fetch_register_using_p, which decodes a stub's register reply into an alloca-sized buffer without bounding writes by the register width.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
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.