# CVE-2025-49796: Libxml: type confusion leads to denial of service (dos)

> An attacker can cause a denial of service by crafting malicious XML input that triggers memory corruption in the libxml2 library.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 8 Oct 2026
- **Also known as:** ALPINE-CVE-2025-49796, AZL-64092, AZL-64130, BELL-CVE-2025-49796, DEBIAN-CVE-2025-49796, ECHO-2f9b-2b25-b4f7, GHSA-83xx-9f6p-vwfj, UBUNTU-CVE-2025-49796

## What is CVE-2025-49796?

CVE-2025-49796 is a critical memory corruption vulnerability in Red Hat OpenShift File Integrity Operator - FIO 1, 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 vulnerability was found in libxml2. Processing certain sch:name elements from the input XML file can trigger a memory corruption issue. This flaw allows an attacker to craft a malicious XML input file that can lead libxml to crash, resulting in a denial of service or other possible undefined behavior due to sensitive data being corrupted in memory.

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

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


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

Apply the vendor's patch.

## Is CVE-2025-49796 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-49796 is a critical memory corruption vulnerability in Red Hat OpenShift File Integrity Operator - FIO 1, 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-49796 in the wild and no public exploit code.

Affected product: Red Hat OpenShift File Integrity Operator - FIO 1. 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-49796/ (Markdown: https://insights.sbomify.com/CVE-2025-49796/index.md)
```

## Sources

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

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