CVE-2026-6653

CVE-2026-6653 is a critical-severity vulnerability in Xmlsoft Libxml2 with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-416.

Key facts

Description

Use After Free in libxml2's xmlParseInternalSubset from GNOME libxml2 version 2.9.11 to 2.11.0 allows a remote attacker to cause a denial-of-service via maliciously crafted XML input with improper entity resolution handling.

Frequently asked questions

What is CVE-2026-6653?
Use After Free in libxml2's xmlParseInternalSubset from GNOME libxml2 version 2.9.11 to 2.11.0 allows a remote attacker to cause a denial-of-service via maliciously crafted XML input with improper entity resolution handling.
How severe is CVE-2026-6653?
CVE-2026-6653 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-6653 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (27th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-6653?
CVE-2026-6653 affects Xmlsoft Libxml2. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-6653?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2026-6653 have an EU (EUVD) identifier?
Yes. CVE-2026-6653 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-38232.
When was CVE-2026-6653 published?
CVE-2026-6653 was published on 2026-06-22 and last updated on 2026-07-14.

References

Affected products (1)

More vulnerabilities in Xmlsoft Libxml2

All CVEs affecting Xmlsoft Libxml2 →

Other CWE-416 (Use After Free) vulnerabilities

Browse all CWE-416 (Use After Free) vulnerabilities →