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

> A malicious HTTP peer can crash applications using libsoup by sending a malformed Content-Disposition header, causing a null pointer dereference.

- **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:** 14 Apr 2025
- **Updated:** 29 Jun 2026
- **Also known as:** AZL-60389, AZL-60402, DEBIAN-CVE-2025-32913, GHSA-9589-mpwg-8xq6, ROOT-OS-DEBIAN-12-CVE-2025-32913, UBUNTU-CVE-2025-32913

## What is CVE-2025-32913?

CVE-2025-32913 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 14 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 libsoup, where the soup_message_headers_get_content_disposition() function is vulnerable to a NULL pointer dereference. This flaw allows a malicious HTTP peer to crash a libsoup client or server that uses this function.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

Apply the vendor's patch.

## Is CVE-2025-32913 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32913 is a high-severity vulnerability in Red Hat Enterprise Linux 10, published on 14 Apr 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-32913 in the wild and no public exploit code.

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-32913/ (Markdown: https://insights.sbomify.com/CVE-2025-32913/index.md)
```

## Sources

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

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