# CVE-2025-60018: Memory corruption in Red Hat Enterprise Linux 10

> An out-of-bounds read in glib-networking's OpenSSL backend allows attackers to cause denial of service or disclose sensitive memory contents.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/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-60018, ECHO-ac1d-7850-4b59, GHSA-3jwx-4xp9-65px

## What is CVE-2025-60018?

CVE-2025-60018 is a medium-severity memory corruption 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 a call to BIO_write(), resulting in an out of bounds read.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Apply the vendor's patch.

## Is CVE-2025-60018 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60018 is a medium-severity memory corruption 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-60018 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-60018/ (Markdown: https://insights.sbomify.com/CVE-2025-60018/index.md)
```

## Sources

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

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