{"answers":{"affected":"3 open source packages ship an affected version, including py-xml. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26709 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26709 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26709 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."},"fix_prompt":"Check this codebase for CVE-2020-26709 and fix it if it is affected.\n\nWhat it is: CVE-2020-26709 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.\nExploitation: There is no known exploitation of CVE-2020-26709 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- py-xml (PyPI): affected all versions; no fix listed\n- py-xml (PyPI): affected all versions up to 1.0; no fix listed\n- py-xml (PyPI): affected all versions up to 1.0; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2020-26709/ (Markdown: https://insights.sbomify.com/CVE-2020-26709/index.md)","id":"CVE-2020-26709","markdown":"https://insights.sbomify.com/CVE-2020-26709/index.md","name":"CVE-2020-26709","record":{"aliases":["GHSA-j6v2-mwxm-f952","PYSEC-2023-95"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python XML library","requires_auth":"none","summary":"Attackers can execute arbitrary code via crafted XML files in the py-xml library, requiring users to upgrade to a secure version.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"py-xml","vendor":"py-xml_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"py-xml XML External Entity Injection vulnerability","id":"CVE-2020-26709","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"xxe","year":"2020"},"n_packages":3,"n_references":1,"next":{"headline":"easy-parse XML External Entity Injection vulnerability","id":"CVE-2020-26710"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":[],"package":"py-xml","purl":"pkg:pypi/py-xml","source":"PYSEC-2023-95"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.0"],"package":"py-xml","purl":null,"source":"GHSA-j6v2-mwxm-f952"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.0"],"package":"py-xml","purl":"pkg:pypi/py-xml","source":"GHSA-j6v2-mwxm-f952"}],"prev":{"headline":"requests-xml XML External Entity Injection vulnerability","id":"CVE-2020-26708"},"products":["n/a"],"published":"2023-06-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-11-27","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code via crafted XML files in the py-xml library, requiring users to upgrade to a secure version.","url":"https://insights.sbomify.com/CVE-2020-26709/"}