llamaCVEVulnerability Intelligence
/
Red Hat Enterprise Linux

CVE-2026-121994

Red Hat remote code execution in GDB via stack buffer overflow

A remote attacker controlling a debug target can run arbitrary code in the GDB process if a user triggers it.

Solo en configuraciones específicasSin parche publicadostack buffer overflow
Descargar PNG JSON
CVSS 3.1
8.8
Alta
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Fuente: CNA
ExplotaciónExploit públicoSSVC de CISA-ADP decía «ninguna» · ajustado por exploit detectado
Exploits públicos11 fuente · 1 confirmado en GitHub
ParcheSin parcheEl fabricante no ha publicado corrección
Exposición15 dDesde la divulgación, 5 nov 2026, 11:08 a. m.
Detección11 minDesde la divulgación hasta su ingreso al índice
Decisión SSVC · ajustadaAtender
Priorizar en el próximo ciclo de cambios
Exploit público disponible (1), no automatizable e impacto técnico total. Decisión recalculada: la evaluación SSVC original indicaba explotación «ninguna». Se eleva a «Atender» por existir un exploit funcional público. No hay versión corregida: aplique mitigaciones.
Esto en un pentest sería tu hallazgo principal.Tu equipo de infra merece un aviso. Hoy.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Evaluación SSVC +1
Modificada
Explotación
Exploit en GitHub
Remediación
Monitoreo
Detectada +2
Fuente: PoC-in-GitHub +1
5 nov 26
6 nov 26
18 nov 26
21 nov 26
5 nov 26
9 nov 26
13 nov 26
17 nov 26
21 nov 26
FechaFaseEventoDetalle
Divulgación Evaluación SSVC CISA-ADP · explotación ninguna
Divulgación Publicada CVE-2026-121994 divulgada · CVSS 8.8 (CNA)
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: NIST NVD Registro visto por primera vez en NIST NVD
Monitoreo Fuente: ENISA EUVD Registro visto por primera vez en ENISA EUVD
Divulgación Modificada Última actualización del registro
Explotación Exploit en GitHub DeeBumG/CVE-2026-121994-POC
Monitoreo Fuente: PoC-in-GitHub Registro visto por primera vez en PoC-in-GitHub
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 5 nov 2026

GDB, the GNU debugger, contains a stack buffer overflow in its remote protocol handler that lets an attacker-controlled debug target execute arbitrary code in the GDB process. An attacker can reach it remotely, without logging in, but a user must take an action to trigger it.

Affects GDB as shipped with Red Hat Enterprise Linux when a developer connects it to a malicious or compromised debug target. CVSS 8.8 (high). No fixed version is listed in the checked facts.

¿Qué significa?A stack buffer overflow in GDB's fetch_register_using_p, caused by an unchecked length in the p-reply from a debug target, lets an attacker-controlled debug target execute arbitrary code in the GDB process.
¿Quién está afectado?The flaw is present in GDB as shipped with Red Hat Enterprise Linux, and the listed products include RHEL 6, 7, 8, 9, and 10 and Red Hat Hardened Images. Exposure requires connecting GDB to a malicious or compromised debug target. To check a system, look at the installed GDB package version with gdb --version and compare it against Red Hat's advisory for this CVE.
¿Qué hacer?The checked facts list no fixed version and no patch identifiers, so no upgrade target can be named. Until one is published, only connect GDB to trusted debug targets, as the vendor advises.
no-patchOnly connect GDB to trusted debug targets. That is the vendor's stated workaround while no fix is listed.
Descripción original del registro (redhat)

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.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
GDB as shipped with Red Hat Enterprise Linux“This flaw is present in GDB as shipped with Red Hat Enterprise Linux.”
02
A developer connects GDB to a malicious or compromised debug target“A developer who connects GDB to a malicious or compromised debug target is exposed to arbitrary code execution in their GDB process.”
¿Quién debe revisar?Teams running GDB shipped with Red Hat Enterprise Linux 6, 7, 8, 9 or 10, or Red Hat Hardened Images, when they connect GDB to remote debug targets.
MitigaciónOnly connect GDB to trusted debug targets.
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:N
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:N
NingunoBajosAltos
InteracciónUI:R
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
10.0/ 10Muy alto
Vector 8.3 (muy fácil) · +1.7 por exploit público.
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
crash
Sin parche — — —
gdb
Sin parche — — —
gcc-toolset-14-gdb
Sin parche — — —
gcc-toolset-15-gdb
Sin parche — — —
Explotación

Arsenal público

Exploit-DB
—
0
Metasploit
—
0
Nuclei
—
0
PoC en GitHub
DeeBumG/CVE-2026-121994-POC
1
Ver los 1 repositorios de GitHub (1 con exploit confirmado)
DeeBumG/CVE-2026-121994-POCexploit

Los repositorios públicos incluyen exploits, escáneres, laboratorios y reglas de detección. No ejecute código de terceros sin revisarlo en un entorno aislado.

Registro
MitigaciónThere is no mitigation for this vulnerability. Users should only connect GDB to trusted debug targets. --- CME Mitigation Guidance (2026-11-06) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce bounds checking against register size when decoding remote serial protocol register replies in the GDB client remote protocol handler: upgrade to the corresponding fixed Red Hat builds, which bounds RSP register reply decoding to the allocated register size rather than terminating only on NUL bytes, closing all 2 injection vectors (oversized RSP register reply, truncated RSP register reply stack disclosure). Until patched, this is a concern on Linux systems running GDB clients connecting to remote RSP debug targets, so Only connect the GDB client to known, trusted debug targets and avoid attaching to unverified or hostile remote RSP stubs. As a compensating measure, Enforce SELinux in enforcing mode to confine the actions of a compromised GDB process, Deploy an EDR agent to detect anomalous process behavior and post-exploitation payloads spawned from GDB, Monitor kernel syscall activity via eBPF to detect unexpected commands or shells spawned by the GDB client, Enable Address Space Layout Randomization to randomize userspace memory addresses, and Enable the NX/XD bit to block direct shellcode execution from stack memory. These controls limit blast radius and contain exploitation, but they do not fix the underlying stack buffer overflow defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)redhat
Referencias
Análisishttps://bugzilla.redhat.com/show_bug.cgi?id=2565676
Exploithttps://github.com/DeeBumG/CVE-2026-121994-POC
Otrahttps://access.redhat.com/security/cve/CVE-2026-121994

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.