CVE-2025-3360: GLib: integer overflow in ISO 8601 parser causes DoS

LOW

Published April 7, 2025

CISO Take

CVE-2025-3360 is an integer overflow and buffer under-read in GLib's g_date_time_new_from_iso8601() that can be triggered by a very long, malformed timestamp. It is rated low (CVSS 3.7, high attack complexity, availability impact only), has no EPSS score, no public exploit, no Nuclei template, and is not in CISA KEV. The blast radius is wide because GLib is a foundational library with 695 tracked dependents, and Red Hat lists many OpenShift AI (rhoai) operator and controller images as affected. Exposure is limited to services that pass untrusted timestamps into this function, and the likely outcome is a crash, not code execution. Treat this as routine patching: take the vendor GLib or glib2 update through your normal container rebuild cycle, and prioritize internet-facing services that parse user-supplied dates.

Sources:NVDRed Hat SecurityGNOME GitLabATLASOpenSSF

What is the risk?

Low overall. The flaw is network-reachable without privileges or user interaction, but exploitation needs a specific code path that feeds attacker-controlled ISO 8601 strings to GLib, which is why complexity is rated high. Confidentiality and integrity are unaffected and the impact is limited to partial availability loss (a crash or erratic behavior). There is no known exploitation, no public PoC and no EPSS signal. The Red Hat OpenShift AI images that bundle GLib broaden exposure, but most of those components are internal control-plane services that rarely parse untrusted timestamps.

How does the attack unfold?

Initial Access

Attacker identifies a network-exposed service in the AI platform that parses ISO 8601 timestamps with GLib.

AML.T0049

Exploitation

Attacker submits an overly long, invalid timestamp that triggers the integer overflow and buffer under-read in g_date_time_new_from_iso8601().

Impact

The process crashes or degrades, disrupting model serving, registry or pipeline operations.

AML.T0029

Initial Access

Attacker identifies a network-exposed service in the AI platform that parses ISO 8601 timestamps with GLib.

AML.T0049

Exploitation

Attacker submits an overly long, invalid timestamp that triggers the integer overflow and buffer under-read in g_date_time_new_from_iso8601().

Impact

The process crashes or degrades, disrupting model serving, registry or pipeline operations.

AML.T0029

What systems are affected?

Package	Ecosystem	Vulnerable Range	Patched
MLflow	pip	—	No patch
28.6KOpenSSF 5.4695 dependentsPushed 5d ago15% patched~68d to patchFull package profile →
MLflow	pip	—	No patch
28.6KOpenSSF 5.4695 dependentsPushed 5d ago15% patched~68d to patchFull package profile →
MLflow	pip	—	No patch
28.6KOpenSSF 5.4695 dependentsPushed 5d ago15% patched~68d to patchFull package profile →
MLflow	pip	—	No patch
28.6KOpenSSF 5.4695 dependentsPushed 5d ago15% patched~68d to patchFull package profile →
bootc	—	—	No patch
glib	—	—	No patch
glib2	—	—	No patch
glycin-loaders	—	—	No patch
librsvg2	—	—	No patch
loupe	—	—	No patch
mingw-glib2	—	—	No patch
rhoai/odh-ai-gateway-operator-rhel9	—	—	No patch
rhoai/odh-core-bff-rhel9	—	—	No patch
rhoai/odh-dashboard-operator-rhel9	—	—	No patch
rhoai/odh-dashboard-rhel9	—	—	No patch
rhoai/odh-data-science-pipelines-operator-controller-rhel9	—	—	No patch
rhoai/odh-kf-notebook-controller-rhel9	—	—	No patch
rhoai/odh-kserve-controller-rhel9	—	—	No patch
rhoai/odh-kserve-llmisvc-controller-rhel9	—	—	No patch
rhoai/odh-kserve-module-operator-rhel9	—	—	No patch
rhoai/odh-kube-rbac-proxy-rhel9	—	—	No patch
rhoai/odh-kuberay-operator-controller-rhel9	—	—	No patch
rhoai/odh-llama-stack-k8s-operator-rhel9	—	—	No patch
rhoai/odh-maas-controller-rhel9	—	—	No patch
rhoai/odh-mod-arch-agent-ops-rhel9	—	—	No patch
rhoai/odh-mod-arch-automl-rhel9	—	—	No patch
rhoai/odh-mod-arch-autorag-rhel9	—	—	No patch
rhoai/odh-mod-arch-eval-hub-rhel9	—	—	No patch
rhoai/odh-mod-arch-gen-ai-rhel9	—	—	No patch
rhoai/odh-mod-arch-maas-rhel9	—	—	No patch
rhoai/odh-mod-arch-model-registry-rhel9	—	—	No patch
rhoai/odh-model-controller-rhel9	—	—	No patch
rhoai/odh-model-registry-operator-rhel9	—	—	No patch
rhoai/odh-model-serving-api-rhel9	—	—	No patch
rhoai/odh-notebook-controller-rhel9	—	—	No patch
rhoai/odh-ogx-k8s-operator-rhel9	—	—	No patch
rhoai/odh-ogx-module-operator-rhel9	—	—	No patch
rhoai/odh-training-operator-rhel9	—	—	No patch
rhoai/odh-trustyai-service-operator-rhel9	—	—	No patch
rhoai/odh-workbenches-operator-rhel9	—	—	No patch

How severe is it?

CVSS 3.1

3.7 / 10

EPSS

N/A

Exploitation Status

No known exploitation

Sophistication

Moderate

What is the attack surface?

AVNetwork

ACHigh

PRNone

UINone

SUnchanged

CNone

INone

ALow

What should I do?

1 step

1) Apply the vendor fix for glib2 per Red Hat advisory CVE-2025-3360, or upgrade to a GLib release containing the upstream fix (GNOME GLib issue 3647). 2) Rebuild and redeploy affected rhoai/odh container images from updated RHEL 9 base layers and OpenShift AI releases. 3) Scan container registries for images with vulnerable glib2 packages and prioritize externally reachable services. 4) Where patching is delayed, validate and length-limit timestamp inputs at the API gateway or application layer before they reach GLib. 5) Monitor for unexpected crashes or restart loops in services that parse ISO 8601 inputs.

How is it classified?

DoSFrameworkInferenceAML.T0029- Denial of AI Service AML.T0049- Exploit Public-Facing Application

Which compliance frameworks are affected?

This CVE is relevant to:

EU AI Act

Art. 15-Accuracy, robustness and cybersecurity

ISO 42001

A.6.2.6-AI system operation and monitoring

NIST AI RMF

MANAGE 2.3-Response to unknown risks and resilience of AI systems

Frequently Asked Questions

What is CVE-2025-3360?

Is CVE-2025-3360 actively exploited?

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

How to fix CVE-2025-3360?

1) Apply the vendor fix for glib2 per Red Hat advisory CVE-2025-3360, or upgrade to a GLib release containing the upstream fix (GNOME GLib issue 3647). 2) Rebuild and redeploy affected rhoai/odh container images from updated RHEL 9 base layers and OpenShift AI releases. 3) Scan container registries for images with vulnerable glib2 packages and prioritize externally reachable services. 4) Where patching is delayed, validate and length-limit timestamp inputs at the API gateway or application layer before they reach GLib. 5) Monitor for unexpected crashes or restart loops in services that parse ISO 8601 inputs.

What systems are affected by CVE-2025-3360?

This vulnerability affects the following AI/ML architecture patterns: model serving, MLOps platforms, Kubernetes-based ML operators, training pipelines, notebook environments, container base images.

What is the CVSS score for CVE-2025-3360?

CVE-2025-3360 has a CVSS v3.1 base score of 3.7 (LOW).

What is the AI security impact?

Affected AI Architectures

model servingMLOps platformsKubernetes-based ML operatorstraining pipelinesnotebook environmentscontainer base images

MITRE ATLAS Techniques

AML.T0029Denial of AI Service

AML.T0049Exploit Public-Facing Application

Compliance Controls Affected

EU AI Act: Art. 15

ISO 42001: A.6.2.6

NIST AI RMF: MANAGE 2.3

What are the technical details?

Original Advisory

A flaw was found in GLib. An integer overflow and buffer under-read occur when parsing a long invalid ISO 8601 timestamp with the g_date_time_new_from_iso8601() function.

Exploitation Scenario

An attacker finds an internet-exposed AI platform component, such as a model registry or inference gateway API, that parses client-supplied ISO 8601 timestamps with GLib. They send repeated requests carrying an extremely long, invalid timestamp string, triggering the integer overflow and buffer under-read. The process crashes or misbehaves, repeatedly interrupting model serving or pipeline operations until the service is restarted or the input is filtered.

Weaknesses (CWE)

CWE-190Integer Overflow or Wraparound

CWE-190 — Integer Overflow or Wraparound: The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

[Requirements] Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
[Requirements] Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.

Source: MITRE CWE corpus.