VulertSecurity VulertSecurity

Vulnerability Database · PyPI · lxml · Version

lxml 2.0.11

2.0.11 is affected by 14 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 6.1.3.

Critical 0 High 2 Medium 6 Low 0 Unrated 6

All lxml versions & vulnerabilities → Search the database for this package →
Released 12 Dec 2008 Licence BSD-3-Clause Also known from other sources 0 Newer releases 130 Database updated 23/Oct/2026

Release and licence data published by PyPI. Licence information is not legal advice.

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.

01 Vulnerabilities affecting this version

lxml 2.0.11 vulnerabilities

14 vulnerabilities cover lxml 2.0.11. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2021-43818: Vulnerability in lxml - Crafted and SVG Embedded Scripts Bypass HTML Cleaner 8.2 medium 4.6.5 13 Dec 2021
CVE-2026-41066: lxml Local File Access Vulnerability 7.5 high 6.1.0 24 Apr 2026
CVE-2026-41066: lxml Default Configuration Allows XXE to Local Files 7.5 high 6.1.0 21 Apr 2026
CVE-2014-3146: lxml Cross-site Scripting Via Control Characters 6.1 medium 3.3.5 14 May 2022
CVE-2018-19787: Improper Neutralization of Input During Web Page Generation in LXML 6.1 medium 4.2.5 13 May 2022
CVE-2021-28957: Cross-Site Scripting Vulnerability in lxml 6.1 medium 4.6.3 22 Mar 2021
CVE-2020-27783: Cross-site Scripting Vulnerability in lxml 6.1 medium 4.6.2 07 Jan 2021
CVE-2022-2309: lxml NULL Pointer Dereference allows attackers to cause a denial of service 5.3 medium 4.9.1 06 Jul 2022
CVE-2022-2309: NULL Pointer Dereference in lxml N/A unrated 86368e9cf70a0ad23cccd5ee32de847149af0c6f 05 Jul 2022
CVE-2021-43818: lxml HTML Cleaner Vulnerability Allows Script Content Bypass N/A unrated f2330237440df7e8f39c3ad1b1aa8852be3b27c0 13 Dec 2021
CVE-2021-28957: XSS Vulnerability in python-lxml's clean module N/A unrated a5f9cb52079dc57477c460dbe6ba0f775e14a999 21 Mar 2021
CVE-2020-27783: XSS vulnerability in python-lxml's clean module N/A unrated 4.6.2 03 Dec 2020
CVE-2018-19787: XSS Vulnerability in lxml N/A unrated 6be1d081b49c97cfd7b3fbd934a193b668629109 02 Dec 2018
CVE-2014-3146: Cross-Site Scripting (XSS) in lxml N/A unrated 3.3.5 14 May 2014

Looking for another version, or everything Vulert holds for lxml?

All versions → Full vulnerability list →

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

About lxml 2.0.11

Is lxml 2.0.11 vulnerable?

Yes. 14 vulnerabilities in the Vulert database cover lxml 2.0.11: 0 critical, 2 high, 6 medium and 0 low, plus 6 not yet rated. The upgrade Vulert recommends is 6.1.3, and each entry above names the fixed version to move to.

Which version of lxml should I use instead of 2.0.11?

6.1.3 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 2.0.11 the latest release of lxml?

No. 2.0.11 was published 12 Dec 2008, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor lxml for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the lxml version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.