A flaw was found in the GNU debugger (GDB). When GDB connects to a remote debug target, a malicious target can cause GDB to overflow a buffer on the stack while parsing the target's replies. This can crash GDB or potentially allow the target to execute arbitrary code in the GDB client process with the privileges of the user running GDB.
CVE-2026-123151
HIGHPre-NVD 7.57.5
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-11-05. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, GitHub Security Advisory
Also known asEUVD-2026-117575 (ENISA EUVD) · GHSA-f82m-v9ch-rh67 (GitHub Security Advisories)Source: ENISA EUVD
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHhigh confidence
- EG Risk
- 49EG Risk 49/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.5%
- EPSS %ILE
- 44th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.5% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 5, 2026
Last Modified
November 6, 2026
Advisory Details (2)
Auto-updated Nov 5, 2026Patch available. Sources: redhat.
Red Hat
2567333 – (CVE-2026-123151) CVE-2026-123151 gdb: gdb: stack buffer overflow in parse_tsv_definition via stale rs->buf tail
https://bugzilla.redhat.com/show_bug.cgi?id=2567333Red HatMentions a patch (unverified)
CVE-2026-123151 - Red Hat Customer Portal
Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a
https://access.redhat.com/security/cve/CVE-2026-123151Vendor Advisories for CVE-2026-123151(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| gdb | 13.1-3 ... 18.1-3~bpo13+1 (41 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| gdb | 16.3-1 ... 18.1-3~bpo13+1 (22 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| gdb | 16.3-1 ... 18.1-3~bpo13+1 (22 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 14× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
- 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
- 2026-11-06 08:28 UTCEchelonGraph re-scored
- 2026-11-06 08:28 UTCGHSA enrichmentGHSA-f82m-v9ch-rh67 · GitHub severity HIGH · GitHub CVSS 7.5
- 2026-11-05 22:28 UTCGHSA enrichmentGHSA-f82m-v9ch-rh67
- 2026-11-05 21:23 UTCEchelonGraph re-scoredFirst assessed: 7.5 HIGH
- 2026-11-05 21:23 UTCGHSA enrichmentGHSA-f82m-v9ch-rh67
- 2026-11-05 21:22 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-11-05 17:26 UTCNVD update
- 2026-11-05 17:04 UTCENISA EUVD ID recordedEUVD-2026-117575 · Source: ENISA EUVD
- 2026-11-05 16:22 UTCEchelonGraph re-scored
- 2026-11-05 16:18 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownDebian:12:gdb
Frequently asked(5)
What is CVE-2026-123151?
CVE-2026-123151 is a high-severity vulnerability; its CVE record was published on November 5, 2026. A flaw was found in the GNU debugger (GDB). When GDB connects to a remote debug target, a malicious target can cause GDB to overflow a buffer on the stack while parsing the target's replies. This can crash GDB or potentially allow the target to execute arbitrary code in the GDB client process with…
When was CVE-2026-123151 made public?
CVE-2026-123151 was made public on November 5, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on November 5, 2026. EchelonGraph's copy of the record carries a last-modified date of November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-123151 actively exploited?
CVE-2026-123151 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-123151?
CVE-2026-123151 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-123151?
A fix for CVE-2026-123151 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-123151 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-123151
Is Your Infrastructure Affected by CVE-2026-123151?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.