BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-41066High confidence

lxml: Default configuration of iterparse() and ETCompatXMLParser() allows XXE to local files

lxml · lxml

Official source article: GitHub GHSA-VFMQ-68HX-4JFW ↗. Check the applicable product and release in the original source.

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 30 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 24 Apr 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.32% for the current model date.

Compensating controls

  • Apply the linked authoritative mitigation while planning the permanent fix.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs lxml lxml and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 30 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 1 affected package state shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelxmlAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelxmlVendor fix publishedDebian records a fixed source-package version for this release.4.9.2-1+deb12u1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelxmlVendor fix publishedDebian records a fixed source-package version for this release.6.1.0-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelxmlVendor fix publishedDebian records a fixed source-package version for this release.6.1.0-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelxmlUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges2 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
PyPIlxmlECOSYSTEM: introduced 0; fixed 6.1.06.1.0OSV record ↗aggregator derived · 10 Sep 2026
piplxml< 6.1.06.1.0GitHub advisory ↗upstream repository advisory · 6 Jun 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-41066 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitylxml: python: lxml: Information disclosure via untrusted XML input leading to local file read
29 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8
  • pen-drive/pen-drive-scanner-rhel9 as a component of Pen Drive Powered by Red Hat Lightspeed
  • rhaiis/vllm-neuron-rhel9 as a component of Red Hat AI Inference Server
  • ansible-automation-platform-25/ee-supported-rhel8 as a component of Red Hat Ansible Automation Platform 2
  • ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2
  • ansible-automation-platform-26/ee-supported-rhel9 as a component of Red Hat Ansible Automation Platform 2
  • ansible-automation-platform-26/gateway-rhel9 as a component of Red Hat Ansible Automation Platform 2
  • ansible-automation-platform-26/hub-rhel9 as a component of Red Hat Ansible Automation Platform 2
  • automation-controller.src as a component of Red Hat Ansible Automation Platform 2
  • python3-lxml as a component of Red Hat Enterprise Linux 10
  • python-lxml.src as a component of Red Hat Enterprise Linux 6
  • python-lxml-docs as a component of Red Hat Enterprise Linux 7
Summary
A flaw was found in lxml, a library for processing XML and HTML in Python. A remote attacker can exploit this vulnerability by sending untrusted XML input to an application using lxml's default parser configuration. This allows the attacker to read local files on the system, leading to information disclosure.
Remediation
Applications using the lxml library to process untrusted XML input should explicitly configure the parser to prevent external entity resolution. This can be achieved by setting the `resolve_entities` option to `False` or `'internal'` when initializing the parser. For example, `etree.XML(xml_input, parser=etree.XMLParser(resolve_entities=False))` or `etree.HTML(html_input, parser=etree.HTMLParser(resolve_entities='internal'))`.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-25572

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 30 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

lxml is a library for processing XML and HTML in the Python language. Prior to 6.1.0, using either of the two parsers in the default configuration (with resolve_entities=True) allows untrusted XML input to read local files. Setting the resolve_entities option explicitly to resolve_entities='internal' or resolve_entities=False disables the local file access. This vulnerability is fixed in 6.1.0.

What

lxml is a library for processing XML and HTML in the Python language. Prior to 6.1.0, using either of the two parsers in the default configuration (with resolve_entities=True) allows untrusted XML input to read local files. Setting the resolve_entities option explicitly to resolve_entities='internal' or resolve_entities=False disables the local file access. This vulnerability is fixed in 6.1.0.

Why

The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

lxml is a library for processing XML and HTML in the Python language. Prior to 6.1.0, using either of the two parsers in the default configuration (with resolve_entities=True) allows untrusted XML input to read local files. Setting the resolve_entities option explicitly to resolve_entities='internal' or resolve_entities=False disables the local file access. This vulnerability is fixed in 6.1.0.

Why

The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Improper Restriction of XML External Entity Reference → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-611 ↗

CWE-611: Improper Restriction of XML External Entity Reference. The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-611Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-3046IBM Concert: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Concert ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen, um einen SQL-Injection Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-2933Splunk SOAR: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Splunk SOAR ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen SQL-Injection Angriff durchzuführen, um einen Cross-Site Scripting Angriff durchzuführen, und um beliebigen Programmcode auszuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-1219lxml: Schwachstelle ermöglicht Offenlegung von Informationen

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in lxml ausnutzen, um Informationen offenzulegen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260429Security Bulletin 29 Apr 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Apr 2026, published on 29 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1056Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2026-34520 Référence CVE CVE-2026-34525 https://www.cve.org/CVERecord?id=CVE-2026-34525 Référence CVE CVE-2026-34601 https://www.cve.org/CVERecord?id=CVE-2026-34601 Référence CVE CVE-2026-34986 https://www.cve.org/CVERecord?id=CVE-2026-34986 Référence CVE CVE-2026-35536 https://www.cve.org/CVERecord?id=CVE-2026-35536 Référence CVE CVE-2026-39883 https://www.cve.org/CVERecord?id=CVE-2026-39883 Référence CVE CVE-2026-40087 https://www.cve.org/CVERecord?id=CVE-2026-40087 Référence CVE CVE-2026-40460 https://www.cve.org/CVERecord?id=CVE-2026-40460 Référence CVE CVE-2026-40701 https://www.cve.org/CVERecord?id=CVE-2026-40701 Référence CVE CVE-2026-41066 https://www.cve.org/CVERecord?id=CVE-2026-41066 Référence CVE CVE-2026-42215 https://www.cve.org/CVERecord?id=CVE-2026-42215 Référence CVE CVE-2026-42284 https://www.cve.org/CVERecord?id=CVE-2026-42284 Référence CVE CVE-2026-42766 https://www.cve.org/CVERecord?id=CVE-2026-42766 Référence CVE CVE-2026-42934 https://www.cve.org/CVERecord?id=CVE-2026-42934 Référence CVE CVE-2026-42945 https://www.cve.org/CVERecord?id=CVE-2026-42945 Référence CVE CVE-2026-42946 https://www.cve.org/CVERecord?id=CVE-2026-42946 Référence CVE CVE-2026-44243 https://www.cve.org/CVERecord?id=CVE-2026-44243 Référence CVE CVE-2026-44244 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0556Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2026-35237 Référence CVE CVE-2026-35238 https://www.cve.org/CVERecord?id=CVE-2026-35238 Référence CVE CVE-2026-35239 https://www.cve.org/CVERecord?id=CVE-2026-35239 Référence CVE CVE-2026-35240 https://www.cve.org/CVERecord?id=CVE-2026-35240 Référence CVE CVE-2026-35469 https://www.cve.org/CVERecord?id=CVE-2026-35469 Référence CVE CVE-2026-3644 https://www.cve.org/CVERecord?id=CVE-2026-3644 Référence CVE CVE-2026-39883 https://www.cve.org/CVERecord?id=CVE-2026-39883 Référence CVE CVE-2026-39892 https://www.cve.org/CVERecord?id=CVE-2026-39892 Référence CVE CVE-2026-40192 https://www.cve.org/CVERecord?id=CVE-2026-40192 Référence CVE CVE-2026-41066 https://www.cve.org/CVERecord?id=CVE-2026-41066 Référence CVE CVE-2026-4111 https://www.cve.org/CVERecord?id=CVE-2026-4111 Référence CVE CVE-2026-4224 https://www.cve.org/CVERecord?id=CVE-2026-4224 Référence CVE CVE-2026-4424 https://www.cve.org/CVERecord?id=CVE-2026-4424 Référence CVE CVE-2026-4519 https://www.cve.org/CVERecord?id=CVE-2026-4519 Référence CVE CVE-2026-4539 https://www.cve.org/CVERecord?id=CVE-2026-4539 Référence CVE CVE-2026-4786 https://www.cve.org/CVERecord?id=CVE-2026-4786 Référence CVE CVE-2026-4878 https://www.cve.org/CVERecord?id=CVE-2026-4878 Référence CVE CVE-2026-5121 https://www.cve.org/CVERecord?id=CVE-2026-5121 R

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-013539lxmlにおけるXML 外部エンティティの脆弱性

lxmlはPython言語でXMLおよびHTMLを処理するためのライブラリです。6.1.0より前のバージョンでは、デフォルト設定(resolve_entities=True)でいずれかの2つのパーサーを使用すると、信頼されていないXML入力によりローカルファイルを読み取ることが可能でした。resolve_entitiesオプションを明示的にresolve_entities='internal'またはresolve_entities=Falseに設定すると、ローカルファイルへのアクセスが無効になります。この脆弱性は6.1.0で修正されました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Applications using the lxml library to process untrusted XML input should explicitly configure the parser to prevent external entity resolution. This can be achieved by setting the `resolve_entities` option to `False` or `'internal'` when initializing the parser. For example, `etree.XML(xml_input, parser=etree.XMLParser(resolve_entities=False))` or `etree.HTML(html_input, parser=etree.HTMLParser(resolve_entities='internal'))`.
04

Evidence and provenance

Published 24 Apr 2026 · Last source change 24 Apr 2026, 18:04 UTC · CWE-611 · Improper Restriction of XML External Entity Reference

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-25572
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-41066 · cve.blacktree.nl