# CVE-2020-26708: requests-xml XML External Entity Injection vulnerability

> Attackers can execute arbitrary code via crafted XML files in the requests-xml library, requiring users to upgrade to a patched version.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2023
- **Updated:** 27 Nov 2024
- **Also known as:** GHSA-ccrc-9x59-3vc4, PYSEC-2023-96

## What is CVE-2020-26708?

CVE-2020-26708 is a high-severity vulnerability in n/a, published on 29 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

requests-xml v0.2.3 was discovered to contain an XML External Entity Injection (XXE) vulnerability which allows attackers to execute arbitrary code via a crafted XML file.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2020-26708?

3 open source packages ship an affected version, including requests-xml. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `requests-xml` | PyPI | All versions | None |
| `requests-xml` | PyPI | All versions to 0.2.3 | None |
| `requests-xml` | PyPI | All versions to 0.2.3 | None |

Products: Requests-Xml Project Requests-Xml.

## How do I fix CVE-2020-26708?

No fix has been published for CVE-2020-26708 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-26708 being exploited?

There is no known exploitation of CVE-2020-26708 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26708 and fix it if it is affected.

What it is: CVE-2020-26708 is a high-severity vulnerability in n/a, published on 29 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-26708 in the wild and no public exploit code.

Affected packages and fixed versions:
- requests-xml (PyPI): affected all versions; no fix listed
- requests-xml (PyPI): affected all versions up to 0.2.3; no fix listed
- requests-xml (PyPI): affected all versions up to 0.2.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-26708/ (Markdown: https://insights.sbomify.com/CVE-2020-26708/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-26708
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-26708
- OSV: https://osv.dev/vulnerability/CVE-2020-26708

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-26708/
Summaries are generated and may contain mistakes; the official description above is the record.