| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability was found in lxml up to 6.0.x. It has been classified as problematic. The affected element is an unknown function. This manipulation causes xml external entity reference. This vulnerability is tracked as CVE-2026-41066. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability classified as critical was found in lxml up to 6.0.x. Affected by this vulnerability is an unknown code block. The manipulation with an unknown input leads to a xml external entity reference vulnerability. The CWE definition for the vulnerability is CWE-611. 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. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-41066 since 04/16/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available.
The vulnerability scanner Nessus provides a plugin with the ID 310526 (Linux Distros Unpatched Vulnerability : CVE-2026-41066), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 6.1.0 eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (310526) and CERT Bund (WID-SEC-2026-1219). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- SUSE Linux
- SUSE openSUSE
- Open Source lxml
Product
Name
Version
Website
- Product: https://github.com/lxml/lxml/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Xml external entity referenceCWE: CWE-611 / CWE-610
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 310526
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-41066
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: lxml 6.1.0
Timeline
04/16/2026 CVE reserved04/24/2026 Advisory disclosed
04/24/2026 VulDB entry created
07/06/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-vfmq-68hx-4jfw
Status: Confirmed
CVE: CVE-2026-41066 (🔒)
GCVE (CVE): GCVE-0-2026-41066
GCVE (VulDB): GCVE-100-359497
CERT Bund: WID-SEC-2026-1219 - lxml: Schwachstelle ermöglicht Offenlegung von Informationen
Entry
Created: 04/24/2026 20:42Updated: 07/06/2026 04:16
Changes: 04/24/2026 20:42 (63), 04/28/2026 07:23 (2), 07/06/2026 04:16 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.