# CVE-2025-49795: Libxml: null pointer dereference leads to denial of service (dos)

> An attacker can cause a denial of service by sending malicious XML input to applications using libxml2 for XPath processing.

- **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:** 16 Jun 2025
- **Updated:** 12 Oct 2026
- **Also known as:** ALPINE-CVE-2025-49795, AZL-64098, AZL-64121, BELL-CVE-2025-49795, ECHO-44c5-a0a5-783a, GHSA-gg7j-w83p-fxr9, UBUNTU-CVE-2025-49795

## What is CVE-2025-49795?

CVE-2025-49795 is a high-severity vulnerability in GNOME Red Hat Enterprise Linux 10, published on 16 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A NULL pointer dereference vulnerability was found in libxml2 when processing XPath XML expressions. This flaw allows an attacker to craft a malicious XML input to libxml2, leading to a denial of service.

Weakness: CWE-825 (Expired Pointer Dereference)

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


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

Apply the vendor's patch.

## Is CVE-2025-49795 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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