CVE-2025-49796

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data tampering, service disruption.

Exploit odds

1.6% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2025-06-10 22:17 UTC ReservedThe CVE id was reserved by its CNA
2. 2025-06-16 16:15 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-11-04 22:17 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.6% in the next 30 days (EPSS).
• Severity: 9.1 CRITICAL (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2025-06-16 16:15 UTC

Last modified

2026-11-04 22:17 UTC

Exploit probability

1.6% · EPSS, next 30 days

Weakness

CWE-125 · Out-of-bounds read

Record status

Deferred

Attack profile CVSS 3.1 · 9.1

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-49796.md and follow it. Check whether this project is affected by CVE-2025-49796. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge