libxml2 vulnerabilities — 12 matching vulnerabilities

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed — no installation and no source-code access required.

Scan your app free →

Severity	Vulnerability	Package	Ecosystem	Disclosed	Fixed version
8.5 high	Critical Security Flaw in libxml2: Heap and Stack Buffer Overflows	`libxml2`	Rocky Linux	25 Sep 2026	0:2.9.13-14.el9_8.5
5.9 medium	Moderate Vulnerability in libxml2: Denial of Service and Arbitrary Code Execution Risks	`libxml2`	Rocky Linux	31 Aug 2026	0:2.9.13-14.el9_8.4
2.5 low	Critical Stack Buffer Overflow in libxml2: Security Update Required	`libxml2`	Rocky Linux	15 Jul 2026	0:2.9.13-14.el9_8.2
5.5 medium	Buffer Over-read Vulnerability in libxml2: Security Update Required	`libxml2`	Rocky Linux	24 Jun 2026	0:2.9.13-14.el9_8.1
6.2 medium	Moderate Security Vulnerability in libxml2: Infinite Recursion Issue	`libxml2`	Rocky Linux	02 Dec 2025	0:2.9.13-14.el9_7
9.1 critical	Critical Vulnerability in libxml2: Heap Use After Free and Integer Overflow Issues	`libxml2`	Rocky Linux	04 Oct 2025	0:2.9.13-10.el9_6
7.8 high	Critical Security Flaw in libxml2: Heap Use-After-Free Vulnerability	`libxml2`	Rocky Linux	04 Oct 2025	0:2.9.13-11.el9_6
7.5 high	Moderate Security Vulnerability in libxml2: Out-of-Bounds Read Issues	`libxml2`	Rocky Linux	04 Oct 2025	0:2.9.13-12.el9_6
8.1 high	Critical Security Vulnerability in libxml2: Use-After-Free and Buffer Overflow Issues	`libxml2`	Rocky Linux	29 Jul 2025	0:2.9.13-6.el9_5.2
Unrated	Moderate: libxml2 security update	`libxml2`	Rocky Linux	10 May 2024	0:2.9.13-6.el9_4
8.2 high	Moderate: libxml2 security update	`libxml2`	Rocky Linux	23 Jan 2023	0:2.9.13-3.el9_1
7.4 high	Moderate: libxml2 security update	`libxml2`	Rocky Linux	28 Jun 2022	0:2.9.13-1.el9_0.1

Subscribe to Vulert on Telegram

Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.

Join the channel →

Questions

Searching the database

How do I search for a CVE or a package?

Type a CVE id, package name, ecosystem or keyword into the search field. Results include the severity, the affected package, the ecosystem, the disclosure date and the fixed version.

Can I filter by severity or by whether a fix exists?

Yes. The filters on the left narrow the list to critical, high, medium or low vulnerabilities, to a single ecosystem, and to vulnerabilities that have a fix available or none yet.

What does "No fix published" mean?

No patched version has been released for that vulnerability yet. The vulnerability page still shows the affected range and any workaround that can reduce exposure in the meantime.