Skip to content

Vendor

lxml vulnerabilities

9 published CVES affecting lxml, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).

Total
9
Critical
1
High
4
Medium
4
Low
0
Unscored
0
CISA KEV
0
Atom feed of lxml alerts

Products

Latest lxml CVEs

Newest publication first

  1. HighCVSS 8.2 EPSS 0.30%

    lxml is a library for processing XML and HTML in the Python language. Prior to 6.1.1, link attributes in lxml.html.defs.link_attrs were missing xlink:href, which can be used for URL bypass attacks in embedded SVG/MathML/etc. content. This vulnerability was fixed in lxml 6.1.1 and...

  2. CriticalCVSS 9.1 EPSS 0.54%

    An XML External Entity (XXE) vulnerability in the ebookmeta.get_metadata function of lxml before v4.9.1 allows attackers to access sensitive information or cause a Denial of Service (DoS) via crafted XML input.

  3. HighCVSS 7.5 EPSS 2.4%

    NULL Pointer Dereference allows attackers to cause a denial of service (or application crash). This only applies when lxml is used together with libxml2 2.9.10 through 2.9.14. libxml2 2.9.9 and earlier are not affected. It allows triggering crashes through forged input data, give...

  4. MediumCVSS 6.1 EPSS 4.0%

    An XSS vulnerability was discovered in python-lxml's clean module versions before 4.6.3. When disabling the safe_attrs_only and forms arguments, the Cleaner class does not remove the formaction attribute allowing for JS to bypass the sanitizer. A remote attacker could exploit thi...

  5. MediumCVSS 6.1 EPSS 4.0%

    A XSS vulnerability was discovered in python-lxml's clean module. The module's parser didn't properly imitate browsers, which caused different behaviors between the sanitizer and the user's page. A remote attacker could exploit this flaw to run arbitrary HTML/JS code.

  6. MediumCVSS 4.3 EPSS 6.3% Public exploit

    Incomplete blacklist vulnerability in the lxml.html.clean module in lxml before 3.3.5 allows remote attackers to conduct cross-site scripting (XSS) attacks via control characters in the link scheme to the clean_html function.

Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.