Vulnerability Database · PyPI · lxml · Version

lxml 6.1.0

6.1.0 is affected by 1 vulnerability.

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 0 Medium 0 Low 0 Unrated 1

Released 18 Apr 2026 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 6.1.0 vulnerabilities

1 vulnerability cover lxml 6.1.0. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2022-2309: NULL Pointer Dereference in lxml N/A unrated 86368e9cf70a0ad23cccd5ee32de847149af0c6f 05 Jul 2022

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 6.1.0

Is lxml 6.1.0 vulnerable?

Yes. 1 vulnerability in the Vulert database cover lxml 6.1.0: 0 critical, 0 high, 0 medium and 0 low, plus 1 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 6.1.0?

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 6.1.0 the latest release of lxml?

No. 6.1.0 was published 18 Apr 2026, 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.