CVE-2026-102010

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

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, ghsa, secondary
Trending — Patch released this week
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%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.0HIGHhigh confidence
EG Risk
32
EG Risk 32/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
14th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 28, 2026

Last Modified

October 2, 2026

Advisory Details (2)

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

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
redhat Patch Available

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

Vendor Advisories for CVE-2026-102010(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatgcc-main-16.2.1-3.hum12026-10-01redhat
redhatgcc13-main-13.5.0-0.2.hum12026-09-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(7 across 3 ecosystems)
Debian:14(4)
PackageVulnerable rangeFix by version rangeDependents
gcc-1212.4.0-5 ... 12.5.0-9 (14 versions)
  • every version on: no fix on record
—
gcc-1414.2.0-19 ... 14.4.0-2 (25 versions)
  • every version on: no fix on record
—
gcc-1515-20241128-1 ... 15.3.0-4 (51 versions)
  • every version on: no fix on record
—
gcc-1616-20251130-1 ... 16.2.0-3 (25 versions)
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
gcc-1212.4.0-5 ... 12.5.0-9 (14 versions)
  • every version on: no fix on record
—
gcc-1414.2.0-19 ... 14.4.0-2 (25 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
gcc-1212.2.0-14 ... 12.5.0-9 (45 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 53× in last 7d / 53× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-05 10:41 UTCEG score recompute
  2. 2026-10-05 10:41 UTCVendor advisory
  3. 2026-10-05 10:40 UTCGHSA enrichment
  4. 2026-10-04 23:21 UTCEPSS rescore
  5. 2026-10-04 21:29 UTCVendor advisory
  6. 2026-10-04 21:29 UTCGHSA enrichment
  7. 2026-10-04 08:18 UTCVendor advisory
  8. 2026-10-04 08:18 UTCGHSA enrichment
  9. 2026-10-03 19:06 UTCEG score recompute
  10. 2026-10-03 19:06 UTCVendor advisory
  11. 2026-10-03 19:06 UTCGHSA enrichment
  12. 2026-10-03 14:25 UTCEPSS rescore
  13. 2026-10-03 05:54 UTCVendor advisory
  14. 2026-10-03 05:54 UTCGHSA enrichment
  15. 2026-10-02 16:42 UTCEG score recompute
  16. 2026-10-02 16:42 UTCVendor advisory
  17. 2026-10-02 16:42 UTCGHSA enrichment
  18. 2026-10-02 03:29 UTCEG score recompute
  19. 2026-10-02 03:29 UTCVendor advisory
  20. 2026-10-02 03:29 UTCGHSA enrichment
  21. 2026-10-02 02:39 UTCEG score recompute
  22. 2026-10-02 02:39 UTCVendor advisory
  23. 2026-10-02 02:39 UTCGHSA enrichment
  24. 2026-10-01 19:49 UTCEG score recompute
  25. 2026-10-01 19:49 UTCVendor advisory
Show 28 more
  1. 2026-10-01 19:49 UTCGHSA enrichment
  2. 2026-10-01 19:49 UTCEPSS rescore
  3. 2026-10-01 06:38 UTCVendor advisory
  4. 2026-10-01 06:38 UTCGHSA enrichment
  5. 2026-09-30 17:26 UTCEG score recompute
  6. 2026-09-30 17:26 UTCVendor advisory
  7. 2026-09-30 17:26 UTCGHSA enrichment
  8. 2026-09-30 15:02 UTCEPSS rescore
  9. 2026-09-30 14:31 UTCEG score recompute
  10. 2026-09-30 14:31 UTCVendor advisory
  11. 2026-09-30 14:31 UTCGHSA enrichment
  12. 2026-09-30 13:35 UTCEG score recompute
  13. 2026-09-30 13:35 UTCVendor advisory
  14. 2026-09-30 13:35 UTCGHSA enrichment
  15. 2026-09-30 11:19 UTCEG score recompute
  16. 2026-09-30 11:19 UTCGHSA enrichment
  17. 2026-09-30 10:35 UTCEG score recompute
  18. 2026-09-30 10:35 UTCGHSA enrichment
  19. 2026-09-29 22:11 UTCEG score recompute
  20. 2026-09-29 22:11 UTCGHSA enrichment
  21. 2026-09-29 15:20 UTCEPSS rescore
  22. 2026-09-29 10:42 UTCEG score recompute
  23. 2026-09-29 10:42 UTCGHSA enrichment
  24. 2026-09-28 21:19 UTCEG score recompute
  25. 2026-09-28 20:58 UTCEG score recompute
  26. 2026-09-28 19:26 UTCEG score recompute
  27. 2026-09-28 19:02 UTCEG score recompute
  28. 2026-09-28 19:01 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

3 shown

Debian:13:gcc-14 · Debian:12:gcc-12

Frequently asked(5)

What is CVE-2026-102010?
CVE-2026-102010 is a high vulnerability 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 disclosed?
CVE-2026-102010 was first published on September 28, 2026, with the most recent update on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-102010 actively exploited?
CVE-2026-102010 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (14th 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.

Book a Demo →Browse All CVEs