CVE-2026-58014: GLib: off-by-one in key file parser enables DoS

HIGHCISA: TRACK*
Published June 30, 2026
CISO Take

CVE-2026-58014 is an off-by-one error in GLib's g_key_file_get_locale_string_list that causes a 1-byte out-of-bounds access when parsing a key file with an empty value, and can crash the process if the access crosses a page boundary. GLib is a foundational C library, not an AI framework, but it ships inside Red Hat AI container images (RHAIIS vLLM CUDA/ROCm, model-opt, and rhai base images for CPU, CUDA, ROCm, TPU and Spyre), so AI inference stacks inherit the flaw. Real-world risk is modest: EPSS is 0.72% (47th percentile), there is no public exploit, no Nuclei template and no KEV listing, and CISA SSVC says TRACK*. The CVSS vector assumes network reach, but exploitation requires an application that parses attacker-controlled key files, which is uncommon in inference serving. Apply the Red Hat errata (e.g. RHSA-2026:49512 and the related advisories) through normal patch cycles by rebuilding or pulling updated base images, and prioritize any service that parses untrusted .ini or desktop-style config files.

Sources:NVDEPSSATLASRed Hat Security Advisories (access.redhat.com)CISA SSVC

What is the risk?

Moderate-to-low in practice despite the CVSS 7.3 rating. The flaw is a 1-byte out-of-bounds access (CWE-193) with possible low confidentiality, integrity and availability impact. The realistic outcome is a crash when the access crosses a page boundary. EPSS is 0.00722 (47th percentile), there is no public exploit, no scanner template and no KEV listing, and SSVC is TRACK*. Exposure depends on whether an application passes untrusted key-file content to g_key_file_get_locale_string_list, which is rare for AI inference and model-serving workloads. Package-level context (148 other CVEs, 95 dependents) shows a broad but well-maintained dependency.

How does the attack unfold?

Initial Access
Attacker delivers a crafted key file with an empty value to a network-reachable service that parses it with GKeyFile.
AML.T0049
Exploitation
The parser calls g_key_file_get_locale_string_list and performs a 1-byte out-of-bounds access.
Impact
If the access crosses a page boundary, the process crashes and the inference or platform service becomes unavailable.
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 →
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
rhcos——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
7.3 / 10
EPSS
0.6%
chance of exploitation in 30 days
Higher than 47% of all CVEs
Exploitation Status
Exploit Available
Exploitation: MEDIUM
Sophistication
Moderate
Exploitation Confidence
medium
○CISA SSVC: Public PoC
Composite signal derived from CISA KEV, VulnCheck KEV, CISA SSVC, EPSS, Metasploit, Exploit-DB, trickest/cve, Nuclei templates, and inthewild.io exploitation reports.

What is the attack surface?

AVACPRUISCIA
AVNetwork
ACLow
PRNone
UINone
SUnchanged
CLow
ILow
ALow

What should I do?

1 step
  1. 1) Apply the Red Hat errata for your product (RHSA-2026:49512, 55440, 57015, 58981, 61766, 61783, 63135, 63138, 63140, 65762) and update glib2 on hosts and RHCOS nodes. 2) Rebuild or pull updated RHAIIS, rhai base, cert-manager and RHUI container images, then redeploy. 3) Inventory images with an SBOM scanner (Syft, Grype, Trivy) to find glib2 in custom AI images built on affected bases. 4) Do not feed untrusted key-file or INI content to GLib's GKeyFile parser in your own applications. 5) Watch for unexplained crashes or segfaults in inference containers and check for abnormal restarts.

What does CISA's SSVC say?

DecisionTrack*
Exploitationpoc
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-Responses to identified AI risks and unknown risks are in place
OWASP LLM Top 10
LLM03-Supply Chain

Frequently Asked Questions

What is CVE-2026-58014?

CVE-2026-58014 is an off-by-one error in GLib's g_key_file_get_locale_string_list that causes a 1-byte out-of-bounds access when parsing a key file with an empty value, and can crash the process if the access crosses a page boundary. GLib is a foundational C library, not an AI framework, but it ships inside Red Hat AI container images (RHAIIS vLLM CUDA/ROCm, model-opt, and rhai base images for CPU, CUDA, ROCm, TPU and Spyre), so AI inference stacks inherit the flaw. Real-world risk is modest: EPSS is 0.72% (47th percentile), there is no public exploit, no Nuclei template and no KEV listing, and CISA SSVC says TRACK*. The CVSS vector assumes network reach, but exploitation requires an application that parses attacker-controlled key files, which is uncommon in inference serving. Apply the Red Hat errata (e.g. RHSA-2026:49512 and the related advisories) through normal patch cycles by rebuilding or pulling updated base images, and prioritize any service that parses untrusted .ini or desktop-style config files.

Is CVE-2026-58014 actively exploited?

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

How to fix CVE-2026-58014?

1) Apply the Red Hat errata for your product (RHSA-2026:49512, 55440, 57015, 58981, 61766, 61783, 63135, 63138, 63140, 65762) and update glib2 on hosts and RHCOS nodes. 2) Rebuild or pull updated RHAIIS, rhai base, cert-manager and RHUI container images, then redeploy. 3) Inventory images with an SBOM scanner (Syft, Grype, Trivy) to find glib2 in custom AI images built on affected bases. 4) Do not feed untrusted key-file or INI content to GLib's GKeyFile parser in your own applications. 5) Watch for unexplained crashes or segfaults in inference containers and check for abnormal restarts.

What systems are affected by CVE-2026-58014?

This vulnerability affects the following AI/ML architecture patterns: Model serving, Containerized inference, Kubernetes AI platforms, Base container images for AI workloads.

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

CVE-2026-58014 has a CVSS v3.1 base score of 7.3 (HIGH). The EPSS exploitation probability is 0.56%.

What is the AI security impact?

Affected AI Architectures

Model servingContainerized inferenceKubernetes AI platformsBase container images for AI workloads

MITRE ATLAS Techniques

AML.T0029Denial of AI Service
AML.T0049Exploit Public-Facing Application

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. An off-by-one error can occur in the g_key_file_get_locale_string_list function in the gkeyfile.c file when loading a key file with an empty value. This flaw can cause an out-of-bounds access of 1 byte or a denial of service when the out-of-bounds access crosses a page boundary.

Exploitation Scenario

An attacker finds an application in an AI platform that accepts user-supplied configuration or key-file content, such as a plugin manifest, desktop-entry style metadata or an uploaded config, and parses it with GKeyFile. They submit a crafted file with an empty locale string list value that triggers the off-by-one access. If the out-of-bounds byte falls on a page boundary, the process crashes, interrupting the service. Repeating the request can sustain an outage in the inference or orchestration component. Reliable code execution is not expected.

Weaknesses (CWE)

CWE-193 — Off-by-one Error: A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value.

  • [Implementation] When copying character arrays or using character manipulation methods, the correct size parameter must be used to account for the null terminator that needs to be added at the end of the array. Some examples of functions susceptible to this weakness in C include strcpy(), strncpy(), strcat(), strncat(), printf(), sprintf(), scanf() and sscanf().

Source: MITRE CWE corpus.

CVSS Vector

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

References

Timeline

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

Related Vulnerabilities