# CVE-2025-60019: Null dereference in Red Hat Enterprise Linux 10

> An attacker can cause a denial of service in applications using glib-networking by triggering an out-of-memory condition that leads to an invalid memory write.

- **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:** 25 Sep 2025
- **Updated:** 30 Jun 2026
- **Also known as:** DEBIAN-CVE-2025-60019, ECHO-0658-0c59-ac79, GHSA-vwwq-37x8-2qrx, OESA-2025-2830, OESA-2025-2831, OESA-2025-2832

## What is CVE-2025-60019?

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

### Official description

glib-networking's OpenSSL backend fails to properly check the return value of memory allocation routines. An out of memory condition could potentially result in writing to an invalid memory location.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

Apply the vendor's patch.

## Is CVE-2025-60019 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60019 is a low-severity vulnerability in Red Hat Enterprise Linux 10, published on 25 Sep 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-60019 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-60019/ (Markdown: https://insights.sbomify.com/CVE-2025-60019/index.md)
```

## Sources

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

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