Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-121994Gdb: gdb: stack buffer overflow in fetch_register_using_p via unchecked p-reply length

Description

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.

Timeline

  1. ID reserved

    By redhat

  2. · 1 day later

    Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-121994, by who scored it
Scored byCVSSScoreVector
redhatCNA (assigner)3.1High8.8CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVDNVD · Awaiting Analysis3.1High8.8CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.48% · top 58% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

What to do

Workaround: There 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)

References

References2

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-121994 badge
[![CVE-2026-121994](https://cveledger.app/badge/CVE-2026-121994.svg)](https://cveledger.app/cve/CVE-2026-121994)

Record last updated .