# CVE-2025-13502: Webkit: webkitgtk / wpe webkit: out-of-bounds read and integer underflow vulnerability leading to dos

> An attacker can cause a denial of service in WebKitGTK applications by triggering an integer underflow and out-of-bounds read via a crafted payload to the GLib remote inspector server.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Nov 2025
- **Updated:** 29 Jun 2026
- **Also known as:** DEBIAN-CVE-2025-13502, GHSA-r6gx-fcg6-8hhj, UBUNTU-CVE-2025-13502

## What is CVE-2025-13502?

CVE-2025-13502 is a high-severity vulnerability in Red Hat Enterprise Linux 6, published on 25 Nov 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 WebKitGTK and WPE WebKit. This vulnerability allows an out-of-bounds read and integer underflow, leading to a UIProcess crash (DoS) via a crafted payload to the GLib remote inspector server.

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

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


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

Apply the vendor's patch.

## Is CVE-2025-13502 being exploited?

There is no known exploitation of CVE-2025-13502 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13502 is a high-severity vulnerability in Red Hat Enterprise Linux 6, published on 25 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13502 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 6. 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-13502/ (Markdown: https://insights.sbomify.com/CVE-2025-13502/index.md)
```

## Sources

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

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