CVE-2026-102010

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-09-28. A secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-88443 (ENISA EUVD) · GHSA-q3jj-75h6-5xmp (GitHub Security Advisories)Source: ENISA EUVD

7.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in GCC. When an application calls the erase_if function on a binary heap priority queue in libstdc++, the library reallocates storage but fails to update its internal entry pointer. An attacker capable of triggering this operation can exploit this use-after-free condition, leading to a Denial of Service (DoS) via an application crash or potential memory corruption.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity70% × 45%
Impact severity (EG Severity): CVSS 7.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.4%
EPSS %ILE
37th
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.0): severity, escalated by confirmed exploitation. This CVE's 7.0 is its impact severity (EG Severity), not escalated.

EG Severity
7.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-18). 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

September 28, 2026

Last Modified

November 11, 2026

Advisory Details (2)

Auto-updated Sep 28, 2026
Patch available. Sources: redhat.
Red Hat

2478395 – (CVE-2026-102010) CVE-2026-102010 gcc-toolset-15-gcc: gcc: gcc-toolset-16: gcc: Denial of Service via use-after-free in binary heap erase_if

https://bugzilla.redhat.com/show_bug.cgi?id=2478395
Red HatMentions a patch (unverified)

CVE-2026-102010 - 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-102010

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatgcc-0:11.5.0-16.el9_92026-11-11redhat
redhatgcc-0:14.3.1-4.5.el10_22026-11-11redhat
redhatgcc-toolset-15-gcc-0:15.2.1-7.3.el9_82026-11-11redhat
redhatgcc-toolset-15-gcc-0:15.2.1-8.1.el10_32026-11-11redhat
redhatgcc-toolset-15-gcc-0:15.2.1-7.3.el9_92026-11-11redhat
redhatgcc-toolset-16-gcc-0:16.2.1-1.3.el9_92026-11-11redhat
redhatgcc-toolset-16-gcc-0:16.2.1-1.3.el10_32026-11-11redhat
redhatgcc-0:14.4.1-4.el10_32026-11-11redhat
redhatgcc-0:11.5.0-15.el9_82026-11-11redhat
redhatgcc-main-16.2.1-3.2.hum12026-11-05redhat
redhatgcc-toolset-15-gcc-0:15.2.1-7.2.el8_102026-10-27redhat
redhatgcc-toolset-15-gcc-0:15.2.1-7.1.el10_22026-10-27redhat
redhatgcc-0:8.5.0-30.el8_102026-10-26redhat
redhatgcc-main-16.2.1-3.hum12026-10-01redhat
redhatgcc13-main-13.5.0-0.2.hum12026-09-30redhat

These rows come from Red Hat. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(10 across 3 ecosystems)
Debian:14(5)
PackageVulnerable rangeFix by version rangeDependents
gcc-1212.4.0-5 ... 12.5.0-9 (15 versions)
  • every version up to 12.5.0-11: fixed in 12.5.0-11
—
gcc-1313.3.0-16 ... 13.5.0-1 (16 versions)
  • every version up to 13.5.0-2: fixed in 13.5.0-2
—
gcc-1414.2.0-19 ... 14.4.0-2 (25 versions)
  • every version up to 14.4.0-3: fixed in 14.4.0-3
—
gcc-1515-20241128-1 ... 15.3.0-4 (51 versions)
  • every version up to 15.3.0-5: fixed in 15.3.0-5
—
gcc-1616-20251130-1 ... 16.2.0-3 (25 versions)
  • every version up to 16.2.0-4: fixed in 16.2.0-4
—
Debian:13(3)
PackageVulnerable rangeFix by version rangeDependents
gcc-1212.4.0-5 ... 12.5.0-9 (16 versions)
  • every version on: no fix on record
—
gcc-1313.3.0-16 ... 13.5.0-4 (19 versions)
  • every version on: no fix on record
—
gcc-1414.2.0-19 ... 14.4.0-4 (27 versions)
  • every version on: no fix on record
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
gcc-1111.3.0-12 ... 11.5.0-9 (27 versions)
  • every version on: no fix on record
—
gcc-1212.2.0-14 ... 12.5.0-9 (47 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 75× 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.

Showing the most recent 100 of 209 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 109 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:37 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  3. 2026-11-19 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  4. 2026-11-18 17:13 UTCEchelonGraph re-scored
  5. 2026-11-18 17:13 UTCVendor advisory
  6. 2026-11-18 17:13 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  7. 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  8. 2026-11-17 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  9. 2026-11-16 16:47 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  10. 2026-11-15 16:53 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  11. 2026-11-14 16:38 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  12. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  13. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  14. 2026-11-11 20:40 UTCEchelonGraph re-scored
  15. 2026-11-11 20:40 UTCVendor advisory
  16. 2026-11-11 20:40 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  17. 2026-11-11 19:24 UTCEchelonGraph re-scored
  18. 2026-11-11 19:24 UTCVendor advisory
  19. 2026-11-11 19:23 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  20. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  21. 2026-11-11 13:19 UTCEchelonGraph re-scored
  22. 2026-11-11 13:19 UTCVendor advisory
  23. 2026-11-11 13:19 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  24. 2026-11-11 12:27 UTCEchelonGraph re-scored
  25. 2026-11-11 12:27 UTCVendor advisory
Show 75 more
  1. 2026-11-11 12:27 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  2. 2026-11-11 12:04 UTCVendor advisory
  3. 2026-11-11 12:04 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  4. 2026-11-11 11:57 UTCVendor advisory
  5. 2026-11-11 11:57 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  6. 2026-11-11 11:29 UTCEchelonGraph re-scored
  7. 2026-11-11 11:29 UTCVendor advisory
  8. 2026-11-11 11:29 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  9. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  10. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  11. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  12. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  13. 2026-11-07 11:36 UTCEchelonGraph re-scored
  14. 2026-11-07 11:36 UTCVendor advisory
  15. 2026-11-07 11:36 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  16. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  17. 2026-11-06 08:27 UTCEchelonGraph re-scored
  18. 2026-11-06 08:27 UTCVendor advisory
  19. 2026-11-06 08:27 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  20. 2026-11-06 07:58 UTCEchelonGraph re-scored
  21. 2026-11-06 07:58 UTCVendor advisory
  22. 2026-11-06 07:58 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  23. 2026-11-06 07:27 UTCEchelonGraph re-scored
  24. 2026-11-06 07:27 UTCVendor advisory
  25. 2026-11-06 07:27 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  26. 2026-11-06 06:28 UTCEchelonGraph re-scored
  27. 2026-11-06 06:28 UTCVendor advisory
  28. 2026-11-06 06:28 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  29. 2026-11-05 17:27 UTCEchelonGraph re-scored
  30. 2026-11-05 17:27 UTCVendor advisory
  31. 2026-11-05 17:27 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  32. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  33. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  34. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  35. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  36. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  37. 2026-11-01 06:47 UTCEchelonGraph re-scored
  38. 2026-11-01 06:47 UTCVendor advisory
  39. 2026-11-01 06:47 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  40. 2026-11-01 04:33 UTCEchelonGraph re-scored
  41. 2026-11-01 04:33 UTCVendor advisory
  42. 2026-11-01 04:33 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  43. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  44. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  45. 2026-10-30 08:26 UTCEchelonGraph re-scored
  46. 2026-10-30 08:26 UTCVendor advisory
  47. 2026-10-30 08:26 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  48. 2026-10-30 07:56 UTCEchelonGraph re-scored
  49. 2026-10-30 07:56 UTCVendor advisory
  50. 2026-10-30 07:56 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  51. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  52. 2026-10-29 06:26 UTCEchelonGraph re-scored
  53. 2026-10-29 06:26 UTCVendor advisory
  54. 2026-10-29 06:26 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  55. 2026-10-29 05:28 UTCEchelonGraph re-scored
  56. 2026-10-29 05:28 UTCVendor advisory
  57. 2026-10-29 05:28 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  58. 2026-10-28 21:32 UTCEchelonGraph re-scored
  59. 2026-10-28 21:32 UTCVendor advisory
  60. 2026-10-28 21:32 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  61. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  62. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  63. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  64. 2026-10-26 14:38 UTCEchelonGraph re-scored
  65. 2026-10-26 14:38 UTCVendor advisory
  66. 2026-10-26 14:38 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  67. 2026-10-26 14:03 UTCEchelonGraph re-scored
  68. 2026-10-26 14:03 UTCVendor advisory
  69. 2026-10-26 14:03 UTCGHSA enrichmentGHSA-q3jj-75h6-5xmp · GitHub severity HIGH · GitHub CVSS 7.0
  70. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  71. 2026-10-25 14:57 UTCEchelonGraph re-scored
  72. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  73. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  74. 2026-10-23 09:10 UTCEchelonGraph re-scored
  75. 2026-10-23 09:10 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-102010?
CVE-2026-102010 is a high-severity vulnerability; its CVE record was published on September 28, 2026. A flaw was found in GCC. When an application calls the erase_if function on a binary heap priority queue in libstdc++, the library reallocates storage but fails to update its internal entry pointer. An attacker capable of triggering this operation can exploit this use-after-free condition, leading…
When was CVE-2026-102010 made public?
CVE-2026-102010 was made public on September 28, 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 September 28, 2026. EchelonGraph's copy of the record carries a last-modified date of November 11, 2026; the record at its source may have been updated since.
Is CVE-2026-102010 actively exploited?
CVE-2026-102010 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102010?
CVE-2026-102010 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-102010?
A fix for CVE-2026-102010 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102010 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-102010

Explore →

Is Your Infrastructure Affected by CVE-2026-102010?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.