CVE-2026-58012: GLib: g_regex_replace RAW over-read leaks bytes, DoS

MEDIUM
Published June 30, 2026
CISO Take

CVE-2026-58012 is a buffer over-read in GLib's g_regex_replace when the G_REGEX_RAW flag is combined with case-change replacement escapes, leaking 1-5 bytes of adjacent memory and potentially crashing the process if the read crosses a page boundary. GLib is a base library, not an AI component, but it ships in Red Hat AI images (RHAIIS vLLM CUDA/ROCm, model-opt, and rhai base images for CPU, CUDA, ROCm, TPU and Spyre), so inference and training containers inherit the flaw. Practical risk is low to moderate: the CVSS is 6.5 and EPSS is 0.85% (top 43%). There is no public exploit, no Nuclei template, it is not in CISA KEV, and CISA SSVC says TRACK. Exploitation also needs an application that passes attacker-controlled input to g_regex_replace with RAW and case-change escapes, which is uncommon. Apply the Red Hat errata (for example RHSA-2026:49512) at the next image rebuild and rebuild AI base images, prioritizing any that expose network services.

Sources:NVDEPSSCISA SSVCRed Hat advisories (access.redhat.com)ATLAS

What is the risk?

Low to moderate. The CVSS vector is network-reachable with low complexity and no privileges, but the impact is limited to a 1-5 byte confidentiality leak and availability loss only when the over-read crosses a page boundary. Exploitation depends on an application using g_regex_replace with G_REGEX_RAW and case-change escapes on attacker-influenced data. EPSS is low (0.00853), no public exploit exists, and SSVC says TRACK. Exposure for AI workloads is indirect, through bundled system libraries in container images.

How does the attack unfold?

Initial Access
Attacker sends crafted non-UTF-8 input to a network-exposed service that uses GLib regex replacement in RAW mode.
AML.T0049
Exploitation
Case-change escapes cause UTF-8 functions to read past the end of the raw buffer.
Impact
1-5 bytes of adjacent memory leak, or the process crashes when the read crosses a page boundary, disrupting inference or pipeline availability.
AML.T0029

What systems are affected?

PackageEcosystemVulnerable RangePatched
vLLMpip—No patch
96.9K93 dependentsPushed 3d ago26% patched~37d to patchFull package profile →
vLLMpip—No patch
96.9K93 dependentsPushed 3d ago26% patched~37d to patchFull package profile →
vLLMpip—No patch
96.9K93 dependentsPushed 3d ago26% patched~37d to patchFull package profile →
GLib——No patch
cert-manager/cert-manager-istio-csr-rhel9——No patch
cert-manager/cert-manager-operator-rhel9——No patch
cert-manager/cert-manager-trust-manager-rhel9——No patch
cert-manager/jetstack-cert-manager-acmesolver-rhel9——No patch
cert-manager/jetstack-cert-manager-rhel9——No patch
discovery/discovery-server-rhel9——No patch
discovery/discovery-ui-rhel9——No patch
glib2——No patch
mingw-glib2——No patch
rhai/base-image-cpu-rhel9——No patch
rhai/base-image-cuda-rhel9——No patch
rhai/base-image-rocm-rhel9——No patch
rhai/base-image-spyre-rhel9——No patch
rhai/base-image-tpu-rhel9——No patch
rhaiis/model-opt-cuda-rhel9——No patch
rhui5/cds-kubernetes-rhel9——No patch
rhui5/cds-kubernetes-tp-rhel9——No patch
rhui5/cds-rhel9——No patch
rhui5/haproxy-rhel9——No patch
rhui5/installer-rhel9——No patch
rhui5/installer-tp-rhel9——No patch
rhui5/rhua-rhel9——No patch
rhui5/rhua-tp-rhel9——No patch

How severe is it?

CVSS 3.1
6.5 / 10
EPSS
0.5%
chance of exploitation in 30 days
Higher than 43% of all CVEs
Exploitation Status
No known exploitation
Sophistication
Moderate

What is the attack surface?

AVACPRUISCIA
AVNetwork
ACLow
PRNone
UINone
SUnchanged
CLow
INone
ALow

What should I do?

1 step
  1. 1) Install the fixed glib2 packages from the Red Hat errata (RHSA-2026:49512, 55440, 57015, 58981, 61766, 61783, 63135, 63138, 63140, 65762) for the relevant product streams. 2) Rebuild and redeploy AI container images from patched base images, and scan registries for images with vulnerable glib2. 3) Audit in-house C/C++ code and native extensions for g_regex_replace used with G_REGEX_RAW and case-change escapes (\U, \L, \u, \l). 4) Where patching is delayed, avoid passing untrusted input to such code paths. 5) Monitor for unexplained crashes (SIGSEGV) in GLib-linked services, which could indicate DoS attempts.

What does CISA's SSVC say?

DecisionTrack
Exploitationnone
AutomatableYes
Technical Impactpartial

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001
A.6.2.6-AI system operation and monitoring
NIST AI RMF
MANAGE 2.3-Response to previously unknown risks and ongoing risk treatment
OWASP LLM Top 10
LLM03-Supply Chain

Frequently Asked Questions

What is CVE-2026-58012?

CVE-2026-58012 is a buffer over-read in GLib's g_regex_replace when the G_REGEX_RAW flag is combined with case-change replacement escapes, leaking 1-5 bytes of adjacent memory and potentially crashing the process if the read crosses a page boundary. GLib is a base library, not an AI component, but it ships in Red Hat AI images (RHAIIS vLLM CUDA/ROCm, model-opt, and rhai base images for CPU, CUDA, ROCm, TPU and Spyre), so inference and training containers inherit the flaw. Practical risk is low to moderate: the CVSS is 6.5 and EPSS is 0.85% (top 43%). There is no public exploit, no Nuclei template, it is not in CISA KEV, and CISA SSVC says TRACK. Exploitation also needs an application that passes attacker-controlled input to g_regex_replace with RAW and case-change escapes, which is uncommon. Apply the Red Hat errata (for example RHSA-2026:49512) at the next image rebuild and rebuild AI base images, prioritizing any that expose network services.

Is CVE-2026-58012 actively exploited?

No confirmed active exploitation of CVE-2026-58012 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-58012?

1) Install the fixed glib2 packages from the Red Hat errata (RHSA-2026:49512, 55440, 57015, 58981, 61766, 61783, 63135, 63138, 63140, 65762) for the relevant product streams. 2) Rebuild and redeploy AI container images from patched base images, and scan registries for images with vulnerable glib2. 3) Audit in-house C/C++ code and native extensions for g_regex_replace used with G_REGEX_RAW and case-change escapes (\U, \L, \u, \l). 4) Where patching is delayed, avoid passing untrusted input to such code paths. 5) Monitor for unexplained crashes (SIGSEGV) in GLib-linked services, which could indicate DoS attempts.

What systems are affected by CVE-2026-58012?

This vulnerability affects the following AI/ML architecture patterns: model serving, containerized inference, training pipelines, AI base images.

What is the CVSS score for CVE-2026-58012?

CVE-2026-58012 has a CVSS v3.1 base score of 6.5 (MEDIUM). The EPSS exploitation probability is 0.49%.

What is the AI security impact?

Affected AI Architectures

model servingcontainerized inferencetraining pipelinesAI base images

MITRE ATLAS Techniques

AML.T0010.004Container Registry
AML.T0029Denial of AI Service

Compliance Controls Affected

ISO 42001: A.6.2.6
NIST AI RMF: MANAGE 2.3
OWASP LLM Top 10: LLM03

What are the technical details?

Original Advisory

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.

Exploitation Scenario

An attacker finds a network-facing service in an inference or data-processing container whose native code calls g_regex_replace with G_REGEX_RAW and a replacement template containing case-change escapes. They send crafted non-UTF-8 byte sequences that make the UTF-8 routines read past the buffer. This leaks a few bytes of adjacent heap memory, or crashes the process when the read crosses a page boundary, interrupting model serving or the data pipeline. Such a vulnerable code path in a typical AI stack is rare.

Weaknesses (CWE)

CWE-126 — Buffer Over-read: The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.

Source: MITRE CWE corpus.

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

References

Timeline

Published
June 30, 2026
Last Modified
November 10, 2026
First Seen
September 30, 2026

Related Vulnerabilities