CVE-2026-58011: GLib: out-of-bounds read in g_date_time_get_ymd
MEDIUMCISA: TRACK*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.
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?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| vLLM | pip | — | No patch |
| vLLM | pip | — | No patch |
| 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?
What is the attack surface?
What should I do?
1 step1) 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?
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:
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
MITRE ATLAS Techniques
AML.T0029Denial of AI ServiceAML.T0049Exploit Public-Facing ApplicationCompliance Controls Affected
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:LReferences
- access.redhat.com/errata/RHSA-2026:49512vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:55440vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:57015vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:58981vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:61766vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:61783vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:63135vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:63138vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:63140vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:65762vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:65763vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:65767vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:65768vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:65769vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:65770vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:65771vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:65773vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:66018vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72394vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72395vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72399vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72470vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72475vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72476vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:72502vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73859vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73909vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73929vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73930vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73959vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73960vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73961vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:73962vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74458vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74459vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74460vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74461vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74462vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74463vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74674vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74677vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74678vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74679vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74681vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74683vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74685vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74687vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74688vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:74771vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:75652vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:75654vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:75655vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:75657vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:75658vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:75659vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:75660vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:76042vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:80769vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:80771vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82059vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82061vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82066vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82304vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82322vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82336vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82347vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82354vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82368vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82371vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82372vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82415vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82857vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:82888vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:92449vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:92452vendor-advisoryx_refsource_REDHAT
- access.redhat.com/errata/RHSA-2026:97163vendor-advisoryx_refsource_REDHAT
- access.redhat.com/security/cve/CVE-2026-58011vdb-entryx_refsource_REDHAT
- bugzilla.redhat.com/show_bug.cgiissue-trackingx_refsource_REDHAT
- gitlab.gnome.org/GNOME/glib/-/issues/3917
Timeline
Related Vulnerabilities
CVE-2026-6173210.0Decepticon: ChatML token injection yields sandbox RCE
Same package: vllmCVE-2024-110419.8vllm: RCE via unsafe pickle deserialization in MessageQueue
Same package: vllmCVE-2026-259609.8vllm: SSRF allows internal network access
Same package: vllmCVE-2025-472779.8vLLM: RCE via exposed TCPStore in distributed inference
Same package: vllmCVE-2024-90539.8vllm: RCE via unsafe pickle deserialization in RPC server
Same package: vllm