CVE-2026-102010: Red Hat Hardened Images · Expired Pointer Dereference
Affects Red Hat Hardened ImagesSource CVE Database V5
Not known to be exploited · CVSS 7.0 High.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-09-28.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Hardened Imagesgcc13-main | Affected– | Fixed in– |
| Red Hat Hardened Imagesgcc-main | Affected– | Fixed in– |
| Red Hat Enterprise Linux 10gcc | Affected– | Fixed in– |
| Red Hat Enterprise Linux 10gcc-toolset-15-gcc | Affected– | Fixed in– |
| Red Hat Enterprise Linux 10gcc-toolset-16 | Affected– | Fixed in– |
| Red Hat Enterprise Linux 10gcc-toolset-16-gcc | Affected– | Fixed in– |
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.