GNOME Glib Unicode Case Conversion out-of-bounds write

Summaryinfo

A vulnerability was found in GNOME Glib. It has been classified as critical. This vulnerability affects unknown code of the component Unicode Case Conversion. Performing a manipulation results in out-of-bounds write. This vulnerability is known as CVE-2026-1489. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in GNOME Glib (unknown version). It has been classified as critical. This affects an unknown code block of the component Unicode Case Conversion. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. CWE is classifying the issue as CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

A flaw was found in GLib. An integer overflow vulnerability in its Unicode case conversion implementation can lead to memory corruption. By processing specially crafted and extremely large Unicode strings, an attacker could trigger an undersized memory allocation, resulting in out-of-bounds writes. This could cause applications utilizing GLib for string conversion to crash or become unstable.

The advisory is shared at access.redhat.com. This vulnerability is uniquely identified as CVE-2026-1489 since 01/27/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/19/2026).

The vulnerability scanner Nessus provides a plugin with the ID 296897 (Linux Distros Unpatched Vulnerability : CVE-2026-1489), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (296897). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• GNOME

Name

• Glib

License

• open-source

Website

• Vendor: https://www.gnome.org/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion