Skip to main content
CVE-2026-41066VulnerabilityPublished Updated

SUSE lxml · Security update for python-lxml

Affects SUSE lxmlSource GCVE Database

0
Compare

Not known to be exploited · fixed in SUSE package updates : update SUSE lxml when convenient.

Data as of 5 Nov 2026, 00:01 UTC

Severity
Medium

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.15.0_3, 1.36.1_1, 0.5.1_18 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
PyPIlxmlpkg:pypi/lxmlOther threatsAffected
  • =4.7.1
Fixed in–
Homebrewpapispkg:brew/papisOther threatsAffected
  • >=0.14.1 <0.15.0_3
Fixed in
  • 0.15.0_3
Homebrewgtk-docpkg:brew/gtk-docOther threatsAffected
  • <1.36.1_1
Fixed in
  • 1.36.1_1
Homebrewpdflypkg:brew/pdflyOther threatsAffected
  • >=0.5.1_6 <0.5.1_18
Fixed in
  • 0.5.1_18
Homebrewgptlinepkg:brew/gptlineOther threatsAffected
  • <1.0.8_22
Fixed in
  • 1.0.8_22
Homebrewrecon-ngpkg:brew/recon-ngOther threatsAffected
  • >=4.8.3 <5.1.2_4
Fixed in
  • 5.1.2_4

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

AI-suggested

A patch is available in lxml version 6.1.0, which changes the default resolve_entities setting to 'internal' for all parsers, preventing local file access by default. Users should upgrade to lxml 6.1.0 or later. Alternatively, users can mitigate the vulnerability by explicitly setting the resolve_entities option to 'internal' or False in their XML parsing code to disable local file access. There is no indication that the vulnerability is mitigated by default in affected versions prior to 6.1.0.

Description

A vulnerability in the lxml library used by recon-ng allows XML External Entity (XXE) attacks via the default configuration of iterparse() and ETCompatXMLParser(). This enables untrusted XML input to read local files. The issue is addressed in lxml 6.1.0 by changing the default resolve_entities setting to 'internal', preventing local file access. Users can also mitigate by explicitly setting resolve_entities to 'internal' or false.

References

Community reviews

Loading reviews…