{"answers":{"affected":"3 open source packages ship an affected version, including docling. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-44020 in the wild and no public exploit code.","fix":"Upgrade docling to 2.74.0 or later.","what":"CVE-2026-44020 is a high-severity vulnerability in docling-project docling, published on 24 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-44020 and fix it if it is affected.\n\nWhat it is: CVE-2026-44020 is a high-severity vulnerability in docling-project docling, published on 24 Jun 2026. 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-2026-44020 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- docling (PyPI): affected from 2.13.0; fixed in 2.74.0\n- docling (PyPI): affected from 2.13.0; fixed in 2.74.0\n- docling (PyPI): affected from 2.13.0; fixed in 2.74.0\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-2026-44020/ (Markdown: https://insights.sbomify.com/CVE-2026-44020/index.md)","id":"CVE-2026-44020","markdown":"https://insights.sbomify.com/CVE-2026-44020/index.md","name":"CVE-2026-44020","record":{"aliases":["GHSA-m88r-rg27-5xfg","PYSEC-2026-240"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python document parser","requires_auth":"none","summary":"Attackers can exploit unsafe XML parsing in Docling to read server files, trigger SSRF, or cause denial of service via malicious patent XML files.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"docling","vendor":"docling"}],"cvss":{"score":7.5,"severity":"high","source":"cna","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"},{"id":"CWE-776","name":"Improper Restriction of Recursive Entity References in DTDs"}],"description":"Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.13.0 until 2.74.0, the USPTO patent XML parser used the standard xml.sax.parseString() without protection against XML External Entity (XXE) attacks. An attacker could craft malicious USPTO patent XML files with external entity references that could read arbitrary files from the server filesystem, perform Server-Side Request Forgery (SSRF) attacks, or cause denial of service through entity expansion (Billion Laughs attack). The vulnerability affects three USPTO patent format parsers: ICE (v4.x), Grant v2.5, and Application v1.x. This vulnerability is fixed in 2.74.0.","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":true,"headline":"Docling: Unsafe XML Entity Expansion in USPTO Patent Backend","id":"CVE-2026-44020","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"xxe","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Docling: Potential Path Traversal via LaTeX \\includegraphics and \\input Commands","id":"CVE-2026-44022"},"packages":[{"ecosystem":"PyPI","fixed":["2.74.0"],"introduced":["2.13.0"],"last_affected":[],"package":"docling","purl":null,"source":"GHSA-m88r-rg27-5xfg"},{"ecosystem":"PyPI","fixed":["2.74.0"],"introduced":["2.13.0"],"last_affected":[],"package":"docling","purl":"pkg:pypi/docling","source":"GHSA-m88r-rg27-5xfg"},{"ecosystem":"PyPI","fixed":["2.74.0"],"introduced":["2.13.0"],"last_affected":[],"package":"docling","purl":"pkg:pypi/docling","source":"PYSEC-2026-240"}],"prev":{"headline":"Docling Core has insufficient validation of image reference URIs","id":"CVE-2026-44019"},"products":["docling"],"published":"2026-06-24","related":[{"cvss_score":8.2,"headline":"Docling: Unsafe Playwright-based HTML Rendering","id":"CVE-2026-44016","kev_date_added":null,"published":"2026-06-24"},{"cvss_score":7.5,"headline":"Docling has arbitrary file read/write (and command execution when shell-escape is enabled) when rendering untrusted TikZ with the opt-in Tectonic engine","id":"CVE-2026-105744","kev_date_added":null,"published":"2026-10-05"},{"cvss_score":7.5,"headline":"Docling: Unsafe Zip Extraction in EasyOCR Model Download","id":"CVE-2026-44017","kev_date_added":null,"published":"2026-06-24"},{"cvss_score":7.1,"headline":"Docling: Unsafe URI and Path Handling in HTML Backend","id":"CVE-2026-47214","kev_date_added":null,"published":"2026-06-26"},{"cvss_score":6.9,"headline":"Docling: Arbitrary local file read via draw:image xlink:href in the OpenDocument backend","id":"CVE-2026-105751","kev_date_added":null,"published":"2026-10-05"},{"cvss_score":6.7,"headline":"Docling: Plugin entry points are imported before the allow_external_plugins check","id":"CVE-2026-105745","kev_date_added":null,"published":"2026-10-05"}],"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":"2026-08-28","vendors":["docling-project"]},"summary":"Attackers can exploit unsafe XML parsing in Docling to read server files, trigger SSRF, or cause denial of service via malicious patent XML files.","url":"https://insights.sbomify.com/CVE-2026-44020/"}