Skip to main content
CVE-2026-58010VulnerabilityPublished Updated

GLib. An off-by-one error can occur · CWE-126

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-58010· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.88.1 or 2.86.5 when convenient.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
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.16.5
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.88.1, 2.86.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jun 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 15 Nov 2026.

What to do

Upgrade GLib to 2.88.1 or 2.86.5.

Affected software

ProductAffectedFixed in
GNOMEGLibAffected
  • <2.88.1
Fixed in
  • 2.88.1
GNOMEGLibAffected
  • <2.86.5
Fixed in
  • 2.86.5

AI-suggested

A security update addressing this vulnerability is available from Red Hat as part of their glib2 package updates. Users should apply the official patches provided in Red Hat Advisory RHSA-2026:49512. Refer to https://access.redhat.com/articles/11258 for update instructions. No additional mitigation steps are required beyond applying the official fix.

Description

A security flaw in GLib's gvs_tuple_is_normal function causes an off-by-one error leading to a 1-byte out-of-bounds read. This can result in minor information disclosure and potential denial of service if the read crosses a page boundary. The issue arises from an incorrect bounds check using > instead of >= during alignment padding verification.

References

Community reviews

Loading reviews…