CVE-2026-58012
MEDIUMDescription
A flaw was found in GLib. A buffer over-read can occur in the g_regex_replace function when used with the `G_REGEX_RAW` compile flag and case-change replacement escapes because the string_append function processes matched substrings using UTF-8 functions that assume valid UTF-8 input, even when the string is treated as raw bytes. This vulnerability can cause a minor information disclosure of 1-5 bytes and a denial of service when the buffer over-read crosses a page boundary.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
Exploit Intelligence
Low risk: more likely to be exploited than 32% of all known CVEs.
References
Related Vulnerabilities
Other CWE-126 (Buffer Over-read) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-49285 | High | 8.6 | 89% | - | Fix |
| CVE-2017-7668 | High | 7.5 | 57% | - | Fix |
| CVE-2025-21277 | High | 7.5 | 39% | - | Fix |
| CVE-2024-38071 | High | 7.5 | 36% | - | Fix |
| CVE-2009-2495 | Medium | 6.5 | 34% | - | - |
| CVE-2024-20290 | High | 7.5 | 34% | - | Fix |
Common questions
How do I fix CVE-2026-58012?
Published advisories record a fix for 33 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-58012 being actively exploited?
Not that we know of. CVE-2026-58012 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.39% is the estimated probability that it will be exploited in the next 30 days. That is higher than 32% of all scored CVEs.
How severe is CVE-2026-58012?
CVE-2026-58012 has a CVSS v3 base score of 6.5, rated moderate. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-58012 affect?
Published advisories record a fix for glib2.0 (Debian), glib2 (Red Hat / RHEL), glib2 (Rocky), glib2-debuginfo (Red Hat / RHEL), and 29 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-58012
Markdown
[](https://tridentstack.com/cve/CVE-2026-58012)HTML
<a href="https://tridentstack.com/cve/CVE-2026-58012"><img src="https://tridentstack.com/cve/badge/CVE-2026-58012.svg" alt="CVE-2026-58012"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-19.