{"answers":{"affected":"3 open source packages ship an affected version, including docling.","exploited":"There is no known exploitation of CVE-2026-31247 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-31247 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-31247 is a high-severity denial of service vulnerability in n/a, published on 11 May 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-31247 and fix it if it is affected.\n\nWhat it is: CVE-2026-31247 is a high-severity denial of service vulnerability in n/a, published on 11 May 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-31247 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- docling (PyPI): affected all versions up to 2.61.0; no fix listed\n- docling (PyPI): affected all versions up to 2.61.0; no fix listed\n- docling (PyPI): affected all versions up to 2.61.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-2026-31247/ (Markdown: https://insights.sbomify.com/CVE-2026-31247/index.md)","id":"CVE-2026-31247","markdown":"https://insights.sbomify.com/CVE-2026-31247/index.md","name":"CVE-2026-31247","record":{"aliases":["GHSA-cr42-rg2m-mq4q","PYSEC-2026-2455"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python document parser","requires_auth":"none","summary":"An attacker can cause a denial of service by submitting a malicious XML file that triggers excessive resource consumption in the Docling parser.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","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-400","name":"Uncontrolled Resource Consumption"}],"description":"Docling's JATS XML backend is vulnerable to XML Entity Expansion (XXE) attacks thru 2.61.0. The backend uses etree.parse() to parse XML files without disabling entity resolution. An attacker can craft a malicious XML file containing a nested entity expansion payload (XML Bomb). When processed by Docling, the exponential expansion of entities leads to excessive resource consumption, resulting in a denial of service (DoS) condition on the system running the Docling parser.","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":"Docling's JATS XML backend is vulnerable to XML Entity Expansion (XXE) attacks","id":"CVE-2026-31247","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Docling's METS GBS backend is vulnerable to XML Entity Expansion (XXE) attacks","id":"CVE-2026-31248"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.61.0"],"package":"docling","purl":null,"source":"GHSA-cr42-rg2m-mq4q"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.61.0"],"package":"docling","purl":"pkg:pypi/docling","source":"GHSA-cr42-rg2m-mq4q"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["2.61.0"],"package":"docling","purl":"pkg:pypi/docling","source":"PYSEC-2026-2455"}],"prev":{"headline":"GPT-Pilot contains a command injection vulnerability in the Executor.run() method","id":"CVE-2026-31246"},"products":["n/a"],"published":"2026-05-11","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-12","vendors":["n/a"]},"summary":"An attacker can cause a denial of service by submitting a malicious XML file that triggers excessive resource consumption in the Docling parser.","url":"https://insights.sbomify.com/CVE-2026-31247/"}