Libxml2 vulnerabilitiesRanked by how likely they are to be used.
Libxml2 is made by Xmlsoft. We track 99 published vulnerabilities in it, across 182 versions. None of them is on the list of flaws known to be exploited today. If you run Libxml2, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Libxml2 vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Libxml2's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Libxml2 flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 41%CVE-2022-40303High
An issue was discovered in libxml2 before 2.10.3.
- 24%CVE-2004-0110High
Buffer overflow in the (1) nanohttp or (2) nanoftp modules in XMLSoft Libxml 2 (Libxml2) 2.6.0 through 2.6.5 allow remote attackers to execute arbitrary code via a long URL.
- 23%CVE-2008-3529Critical
Heap-based buffer overflow in the xmlParseAttValueComplex function in parser.c in libxml2 before 2.7.0 allows context-dependent attackers to cause a denial of service (crash) or execute arbitrary code via a long XML...
- 23%CVE-2017-7376Critical
Buffer overflow in libxml2 allows remote attackers to execute arbitrary code by leveraging an incorrect limit for port values when handling redirects.
- 22%CVE-2021-3518High
There's a flaw in libxml2 in versions before 2.9.11.
- 22%CVE-2004-0989Critical
Multiple buffer overflows in libXML 2.6.12 and 2.6.13 (libxml2), and possibly other versions, may allow remote attackers to execute arbitrary code via (1) a long FTP URL that is not properly handled by the...
- 17%CVE-2021-3517High
There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11.
- 14%CVE-2016-4447High
The xmlParseElementDecl function in parser.c in libxml2 before 2.9.4 allows context-dependent attackers to cause a denial of service (heap-based buffer underread and application crash) via a crafted file, involving...
- 13%CVE-2011-1944Critical
Integer overflow in xpath.c in libxml2 2.6.x through 2.6.32 and 2.7.x through 2.7.8, and libxml 1.8.16 and earlier, allows context-dependent attackers to cause a denial of service (crash) and possibly execute...
Running Libxml2? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to access an array at a negative 2GB offset, typically leading to a segmentation fault.
- Matched to
- Libxml2 on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 99 published vulnerabilities listed under the name Libxml2, across 182 versions.
None of Libxml2's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Libxml2. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.