Skip to main content
CVE-2024-37388VulnerabilityPublished Updated

CVE-2024-37388: lxml · n/a

Affects lxmlSource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.9.1 as a priority.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.9.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Jun 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade lxml to 4.9.1.

Affected software

ProductAffectedFixed in
PyPIlxmlpkg:pypi/lxmlOther threatsAffected
  • <4.9.1
Fixed in
  • 4.9.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-37388, organizations should immediately upgrade the lxml library to version 4.9.1 or later, where the vulnerability has been addressed. In addition to patching, developers should disable XML external entity processing explicitly by configuring the XML parser to disallow external entities and DTD processing, reducing the attack surface. Implement strict input validation and sanitization for all XML inputs, especially those originating from untrusted or external sources. Employ runtime security controls such as application-layer firewalls or XML security gateways that can detect and block malicious XML payloads. Conduct thorough code reviews and security testing focusing on XML parsing components. Monitor application logs for unusual XML processing errors or access patterns indicative of exploitation attempts. For critical systems, consider isolating XML parsing in sandboxed environments to limit potential damage. Maintain an up-to-date inventory of software dependencies to ensure timely patch management. Finally, educate development and security teams about the risks of XXE vulnerabilities and secure coding practices related to XML processing.

Description

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.

References

Community reviews

Loading reviews…