Skip to main content
CVE-2026-0988VulnerabilityPublished Updated

SUSE · Security update for glib2

Affects SUSESource GCVE Database

0
Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-0988· Low 3.7

Not known to be exploited · CVSS 3.7 Low.

Data as of 6 Nov 2026, 14:04 UTC

CVSS 3.1 base score
3.7Low
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Jan 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 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Hardened Imagesglib2-mainAffected–Fixed in–
Red Hat Enterprise Linux 10bootcAffected–Fixed in–
Red Hat Enterprise Linux 10glib2Affected–Fixed in–
Red Hat Enterprise Linux 10glycin-loadersAffected–Fixed in–
Red Hat Enterprise Linux 10loupeAffected–Fixed in–
Red Hat Enterprise Linux 10mingw-glib2Affected–Fixed in–

AI-suggested

Apply the security update provided by the SUSE Product Security Team to address these vulnerabilities. Since the update fixes the issues, no additional mitigation steps are required beyond installing the patch.

Description

This security update for glib2 addresses multiple vulnerabilities including buffer underflow and out-of-bounds access issues caused by integer wraparound, miscalculated buffer boundaries in Base64 encoding, undersized heap allocation due to integer overflow in Unicode case conversion, and a potential integer overflow in g_buffered_input_stream_peek. These flaws could lead to memory corruption and potentially impact application stability or security.

References

Community reviews

Loading reviews…