Skip to main content
VulnerabilityPublished Updated

CVE-2026-102010: Gcc 3.3 · A flaw was found in GCC

Affects gcc-3.3Source GCVE Database

0
Compare
Authoritative record:CVE-2026-102010· High 7.0

Not known to be exploited · CVSS 7.0 High.

Data as of 17 Nov 2026, 21:23 UTC

CVSS 3.1 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.17.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10gcc-11pkg:deb/ubuntu/gcc-11?arch=source&distro=stonkingOther threatsAffected
  • =11.5.0-11ubuntu2
Fixed in–
Ubuntu 26.10gcc-11-crosspkg:deb/ubuntu/gcc-11-cross?arch=source&distro=stonkingOther threatsAffected
  • =26ubuntu1
Fixed in–
Ubuntu 26.10gcc-11-cross-portspkg:deb/ubuntu/gcc-11-cross-ports?arch=source&distro=stonkingOther threatsAffected
  • =21ubuntu1
Fixed in–
Ubuntu 26.10gcc-12pkg:deb/ubuntu/gcc-12?arch=source&distro=stonkingOther threatsAffected
  • =12.5.0-9ubuntu1
Fixed in–
Ubuntu 26.10gcc-12-crosspkg:deb/ubuntu/gcc-12-cross?arch=source&distro=stonkingOther threatsAffected
  • =26ubuntu1
Fixed in–
Ubuntu 26.10gcc-12-cross-portspkg:deb/ubuntu/gcc-12-cross-ports?arch=source&distro=stonkingOther threatsAffected
  • =23ubuntu1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat advises avoiding calls to erase_if() on __gnu_pbds::priority_queue containers using the binary_heap_tag backend. Where predicate-based removal is needed, use alternative containers or different heap backends. A fixed package is being developed; applying it once available is recommended. No other mitigations are currently available.

Description

A use-after-free vulnerability exists in GCC's libstdc++ binary heap priority queue implementation when the erase_if function is called. This flaw can cause heap memory corruption leading to application crashes or denial of service. Exploitation requires specific use of the non-default pb_ds binary_heap_tag container and invocation of erase_if(). Red Hat rates the impact as moderate due to limited reachability. A fix is being pursued.

References

Community reviews

Loading reviews…