CVE-2026-58012 is a buffer over-read vulnerability in GLib affecting the g_regex_replace function. The flaw occurs when g_regex_replace is used with the G_REGEX_RAW compile flag together with case-change replacement escapes. In this code path, matched substrings are processed by string_append using UTF-8 helper logic, including g_utf8_next_char, even though the input is being handled as raw bytes rather than validated UTF-8 text. This mismatch can cause reads past the end of the intended buffer while processing replacement data. The issue is rooted in treating non-UTF-8 raw byte sequences as if they were valid UTF-8 during replacement handling.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability referenced in an Oracle Linux ELSA advisory affecting glib2-related packages; no further technical details are provided in the content.
A specific vulnerability referenced in an AlmaLinux security advisory affecting glib2 packages; no further technical details are provided in the content.
A GLib buffer over-read vulnerability in g_regex_replace() via glib/gregex.c:string_append() and g_utf8_next_char().
A vulnerability referenced in the Oracle Linux advisory for glib2 packages.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.