Py XmlApplication · Py Xml Project

CVE-2020-26709

HIGH · 7.5 CVSS v3.1 Published 2023-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
py-xml v1.0 was discovered to contain an XML External Entity Injection (XXE) vulnerability which allows attackers to execute arbitrary code via a crafted XML file.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

py-xml v1.0 contains an XML External Entity Injection (XXE) vulnerability that allows attackers to execute arbitrary code by supplying a crafted XML file. This occurs because the XML parser processes external entities without proper restrictions, enabling attacker-controlled XML to access local resources or execute commands.

MitigationDisable external entity processing and DTD parsing in the XML parser configuration, implement strict input validation for XML files, and consider upgrading to a patched version if available. For Python xml parsers, this typically involves setting resolver=False or using defusedxml.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Py XmlApplication
Affected:= 1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if py-xml is installed
    Run 'pip show py-xml' or 'pip list | grep -i py-xml' to check if the package is present in your Python environment
    Affected if py-xml version 1.0 is installed and listed in the output
  2. Verify the installed version
    Check the version output from the pip command above - look for 'Version: 1.0' in the output
    Affected if The installed version is exactly 1.0
  3. Locate code using XML parsing from this library
    Search your codebase for imports of 'from pyxml import xmlproc' or similar py-xml modules, and grep for 'import xml' patterns in files that process user-supplied XML
    Affected if Your application imports or uses py-xml's XML parser to process untrusted XML files
  4. Check if external entity processing is enabled
    Review the XML parsing code for absence of resolver restrictions - look for parser configurations that do NOT set 'resolver=False' or use defusedxml, and verify whether DTD parsing is allowed
    Affected if The XML parser is configured to process external entities and DTDs without disabling them (e.g., no resolver=False, no disabling of external entities)
  5. Test for XXE vulnerability in your XML processing
    If you have access to test/development environment, create a test XML file with an external entity reference (e.g., <!ENTITY xxe SYSTEM "file:///etc/passwd">) and process it with your XML parser to see if the external resource is resolved
    Affected if The parser resolves and expands external entities from the crafted XML file, exposing the vulnerability

You are affected if py-xml version 1.0 is installed AND your application uses this library to parse untrusted XML with external entity processing enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable external entity processing and DTD parsing in the XML parser configuration, implement strict input validation for XML files, and consider upgrading to a patched version if available. For Python xml parsers, this typically involves setting resolver=False or using defusedxml.

Fix this in Py Xml Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-26709 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-26709 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data