CVE-2026-102010
Received Received - Intake

GCC libstdc++ Binary Heap Use-After-Free in erase_if

Publication date: 2026-09-28

Last updated on: 2026-09-28

Assigner: redhat-SADP

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-28
Last Modified
2026-09-28
Generated
2026-09-28
AI Q&A
2026-09-28
EPSS Evaluated
N/A
NVD
CVE-2026-102010
EUVD
EUVD-2026-88443

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
gnu gcc *
gnu libstdc%2b%2b *
gnu gnu_compiler_collection 15.2.1
red_hat gcc_toolset 15.2.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-825 The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-102010 is a use-after-free vulnerability in GCC's libstdc++. When the erase_if function is called on a binary heap priority queue, the library reallocates storage but fails to update an internal pointer. This causes a dangling pointer, leading to memory corruption or crashes when the heap is later accessed.

Detection Guidance

To detect this vulnerability, monitor applications using GCC's Policy-Based Data Structures (pb_ds) library with binary_heap_tag. Check for crashes or memory corruption when erase_if is called on priority queues. Use tools like AddressSanitizer to identify use-after-free conditions during testing.

Impact Analysis

An attacker could exploit this to crash applications using affected GCC components, causing Denial of Service. Memory corruption may also lead to unauthorized code execution or data leaks within the vulnerable process. Exploitation requires specific API usage but no special privileges.

Compliance Impact

This vulnerability could impact compliance by enabling Denial of Service attacks that disrupt critical services, potentially violating availability requirements in GDPR or HIPAA. Memory corruption risks may also affect data integrity and confidentiality within affected systems.

Mitigation Strategies

Avoid calling erase_if on __gnu_pbds::priority_queue instances using binary_heap_tag. Consider using alternative containers or backends if predicate-based removal is required. Monitor for updates from GCC maintainers and apply patches once available.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-102010. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart