How severe is CVE-2026-102010?

CVE-2026-102010 has a CVSS 3.x base score of 7.0, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability high.

Is CVE-2026-102010 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (15th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2026-102010?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2026-102010 published?

CVE-2026-102010 was published on 2026-09-28 and last updated on 2026-10-02.

CVE-2026-102010

CVE-2026-102010 is a high-severity vulnerability with a CVSS 3.x base score of 7.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-825.

Key facts

Severity: High (CVSS 3.x base score 7.0)
EPSS exploit prediction: 0% (15th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-825
Published: 2026-09-28
Last modified: 2026-10-02

Description

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.

Frequently asked questions

What is CVE-2026-102010?: 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.
How severe is CVE-2026-102010?: CVE-2026-102010 has a CVSS 3.x base score of 7.0, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability high.
Is CVE-2026-102010 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (15th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-102010?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-102010 published?: CVE-2026-102010 was published on 2026-09-28 and last updated on 2026-10-02.

References

Other CWE-825 vulnerabilities

CVE-2025-49794 — Critical (CVSS 9.1): A use-after-free vulnerability was found in libxml2. This issue occurs when parsing XPath elements under certain…
CVE-2026-46176 — High (CVSS 7.8): In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix error path fall-through in…
CVE-2026-34001 — High (CVSS 7.8): A flaw was found in the X.Org X server. This use-after-free vulnerability occurs in the XSYNC fence triggering logic,…
CVE-2026-8854 — High (CVSS 7.5): IBM HTTP Server 8.5, and 9.0 is vulnerable to denial of service via the optional module mod_mem_cache.
CVE-2025-49795 — High (CVSS 7.5): A NULL pointer dereference vulnerability was found in libxml2 when processing XPath XML expressions. This flaw allows…
CVE-2023-20212 — High (CVSS 7.5): A vulnerability in the AutoIt module of ClamAV could allow an unauthenticated, remote attacker to cause a denial of…

Browse all CWE-825 vulnerabilities →