# CVE-2025-3360: Integer overflow in Red Hat Enterprise Linux 10

> An integer overflow and buffer under-read in GLib's ISO 8601 parser can cause crashes or leak memory when processing long invalid timestamps.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Apr 2025
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-59585, AZL-59591, BELL-CVE-2025-3360, DEBIAN-CVE-2025-3360, DLA-4128-1, GHSA-3435-f6h9-64p7, MINI-j8v3-9j5p-qqpv, OESA-2025-1525, SUSE-SU-2025:01599-1, SUSE-SU-2025:1367-1, SUSE-SU-2025:1457-1, SUSE-SU-2025:20318-1, UBUNTU-CVE-2025-3360, openSUSE-SU-2025:15007-1

## What is CVE-2025-3360?

CVE-2025-3360 is a low-severity vulnerability in Red Hat Enterprise Linux 10, published on 7 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2025-3360?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `glib2` | SUSE:Linux Enterprise Micro 5.1 | All versions | 2.62.6-150200.3.27.1 |
| `glib2` | SUSE:Linux Enterprise Micro 5.2 | All versions | 2.62.6-150200.3.27.1 |
| `glib2` | SUSE:Linux Enterprise Micro 5.3 | All versions | 2.70.5-150400.3.20.1 |
| `glib2` | SUSE:Linux Enterprise Micro 5.4 | All versions | 2.70.5-150400.3.20.1 |
| `glib2` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.70.5-150400.3.20.1 |
| `glib2` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 2.78.6-150600.4.11.1 |
| `glib2` | SUSE:Linux Micro 6.0 | All versions | 2.76.2-7.1 |
| `glib2` | openSUSE:Leap 15.6 | All versions | 2.78.6-150600.4.11.1 |
| `glib2-doc` | openSUSE:Leap 15.6 | All versions | 2.78.6-150600.4.11.1 |
| `glib2` | openSUSE:Tumbleweed | All versions | 2.84.1-2.1 |

## How do I fix CVE-2025-3360?

Upgrade to a fixed version.

## Is CVE-2025-3360 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3360 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3360 and fix it if it is affected.

What it is: CVE-2025-3360 is a low-severity vulnerability in Red Hat Enterprise Linux 10, published on 7 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3360 exists.

Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-3360/ (Markdown: https://insights.sbomify.com/CVE-2025-3360/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-3360
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-3360
- OSV: https://osv.dev/vulnerability/CVE-2025-3360

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-3360/
Summaries are generated and may contain mistakes; the official description above is the record.