CVE-2026-58011: GLib: out-of-bounds read in g_date_time_get_ymd

MEDIUMCISA: TRACK*
Published June 30, 2026
CISO Take

GLib has a 2-byte out-of-bounds read in g_date_time_get_ymd, triggered when g_date_time_add_full returns an invalid GDateTime. The flaw can corrupt date output and cause logic errors or denial of service. It is a general-purpose system library issue, not an AI-specific one, but it is bundled in Red Hat AI base images (rhai/base-image-*) and the RHAIIS vLLM CUDA/ROCm and model-opt images. Exploitation likelihood is low: EPSS is 0.00816 (top 44%), there is no public exploit, no Nuclei template and no CISA KEV listing, and CISA SSVC says TRACK*. The remote, no-privilege vector is only reachable if an application feeds attacker-controlled date arithmetic into GLib. Apply the Red Hat errata (RHSA-2026:49512 and related) through normal patch cycles and rebuild or redeploy affected AI container images.

Sources:NVDEPSSRed Hat Security Advisories (access.redhat.com)ATLAS

What is the risk?

Medium (CVSS 6.5) with low real-world exploitation probability (EPSS 0.8%, no public exploit, not in KEV, SSVC TRACK*). Impact is limited to a 2-byte over-read causing low integrity and availability effects, with no confidentiality impact. Exposure depends on whether services parse or compute attacker-influenced dates through GLib. The CVSS network vector is theoretical for most AI deployments, where GLib is a transitive OS dependency.

How does the attack unfold?

Initial Access
Attacker sends crafted date or time input to a network-reachable service linked against vulnerable GLib.
AML.T0049
Exploitation
g_date_time_add_full produces an invalid GDateTime, and g_date_time_get_ymd reads 2 bytes out of bounds.
Impact
Corrupted date output causes logic errors or a crash, degrading availability of the inference service.
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
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 42% 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
CNone
ILow
ALow

What should I do?

1 step
  1. 1) Apply Red Hat errata (RHSA-2026:49512, 55440, 57015, 58981, 61766, 61783, 63135, 63138, 63140, 65762) matching your product streams. 2) Rebuild and redeploy AI container images from patched Red Hat base images and scan registries for vulnerable glib2 versions. 3) Inventory images with glib2 and mingw-glib2 using SBOM tooling. 4) Monitor for unexpected crashes or malformed date output in services handling time inputs. 5) Prioritize internet-facing inference endpoints; others can follow the normal patch cadence.

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-Respond to and recover from AI system incidents and risks
OWASP LLM Top 10
LLM03-Supply Chain

Frequently Asked Questions

What is CVE-2026-58011?

GLib has a 2-byte out-of-bounds read in g_date_time_get_ymd, triggered when g_date_time_add_full returns an invalid GDateTime. The flaw can corrupt date output and cause logic errors or denial of service. It is a general-purpose system library issue, not an AI-specific one, but it is bundled in Red Hat AI base images (rhai/base-image-*) and the RHAIIS vLLM CUDA/ROCm and model-opt images. Exploitation likelihood is low: EPSS is 0.00816 (top 44%), there is no public exploit, no Nuclei template and no CISA KEV listing, and CISA SSVC says TRACK*. The remote, no-privilege vector is only reachable if an application feeds attacker-controlled date arithmetic into GLib. Apply the Red Hat errata (RHSA-2026:49512 and related) through normal patch cycles and rebuild or redeploy affected AI container images.

Is CVE-2026-58011 actively exploited?

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

How to fix CVE-2026-58011?

1) Apply Red Hat errata (RHSA-2026:49512, 55440, 57015, 58981, 61766, 61783, 63135, 63138, 63140, 65762) matching your product streams. 2) Rebuild and redeploy AI container images from patched Red Hat base images and scan registries for vulnerable glib2 versions. 3) Inventory images with glib2 and mingw-glib2 using SBOM tooling. 4) Monitor for unexpected crashes or malformed date output in services handling time inputs. 5) Prioritize internet-facing inference endpoints; others can follow the normal patch cadence.

What systems are affected by CVE-2026-58011?

This vulnerability affects the following AI/ML architecture patterns: model serving, inference containers, Red Hat OpenShift AI base images, Kubernetes certificate management.

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

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

What is the AI security impact?

Affected AI Architectures

model servinginference containersRed Hat OpenShift AI base imagesKubernetes certificate management

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 out-of-bounds read of only 2 bytes can occur in the g_date_time_get_ymd function in the glib/gdatetime.c file when an invalid GDateTime object produced by the g_date_time_add_full function is processed. This flaw can corrupt the date output and potentially cause logic errors that may lead to a denial of service.

Exploitation Scenario

An attacker sends crafted date or time inputs to a network-reachable service built on a vulnerable GLib, such as a model-serving wrapper or auxiliary component that uses g_date_time_add_full with attacker-influenced offsets. The invalid GDateTime triggers a 2-byte over-read in g_date_time_get_ymd. The result is corrupted date values that skew logging, scheduling or token expiry logic, or a crash that degrades inference availability. No code execution or data disclosure is indicated.

Weaknesses (CWE)

CWE-125 — Out-of-bounds Read: The product reads data past the end, or before the beginning, of the intended buffer.

  • [Implementation] Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylis
  • [Architecture and Design] Use a language that provides appropriate memory abstractions.

Source: MITRE CWE corpus.

CVSS Vector

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

References

Timeline

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

Related Vulnerabilities