{"answers":{"affected":"3 open source packages ship an affected version, including docling-core.","exploited":"There is no known exploitation of CVE-2026-44019 in the wild and no public exploit code.","fix":"Upgrade docling-core to 2.74.1 or later.","what":"CVE-2026-44019 is a high-severity path traversal vulnerability in docling-project docling-core, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-44019 and fix it if it is affected.\n\nWhat it is: CVE-2026-44019 is a high-severity path traversal vulnerability in docling-project docling-core, published on 16 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-44019 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- docling-core (PyPI): affected from 2.5.0; fixed in 2.74.1\n- docling-core (PyPI): affected from 2.5.0; fixed in 2.74.1\n- docling-core (PyPI): affected from 2.5.0; fixed in 2.74.1\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-44019/ (Markdown: https://insights.sbomify.com/CVE-2026-44019/index.md)","id":"CVE-2026-44019","markdown":"https://insights.sbomify.com/CVE-2026-44019/index.md","name":"CVE-2026-44019","record":{"aliases":["GHSA-j5xp-7m2f-49jv","PYSEC-2026-2456"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python document processing library","requires_auth":"none","summary":"Attackers can access local files or cause denial of service via malicious image references in Docling Core applications.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"},{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"Docling Core defines core data types and transformations for the document processing application Docling. In versions 2.5.0 and above, prior to 2.74.1, docling-core could allow local file:// image references and accepted inline data: content without a decoded-size limit. In applications that accept untrusted image references, this may allow access to local files readable by the process or excessive memory use from large inline payloads. This issue has been fixed in version 2.74.1.","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 Core has insufficient validation of image reference URIs","id":"CVE-2026-44019","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Docling: Unsafe XML Entity Expansion in USPTO Patent Backend","id":"CVE-2026-44020"},"packages":[{"ecosystem":"PyPI","fixed":["2.74.1"],"introduced":["2.5.0"],"last_affected":[],"package":"docling-core","purl":null,"source":"GHSA-j5xp-7m2f-49jv"},{"ecosystem":"PyPI","fixed":["2.74.1"],"introduced":["2.5.0"],"last_affected":[],"package":"docling-core","purl":"pkg:pypi/docling-core","source":"GHSA-j5xp-7m2f-49jv"},{"ecosystem":"PyPI","fixed":["2.74.1"],"introduced":["2.5.0"],"last_affected":[],"package":"docling-core","purl":"pkg:pypi/docling-core","source":"PYSEC-2026-2456"}],"prev":{"headline":"Docling: Unsafe Archive Extraction and XML Parsing in METS-GBS Backend","id":"CVE-2026-44018"},"products":["docling-core"],"published":"2026-07-16","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-07-17","vendors":["docling-project"]},"summary":"Attackers can access local files or cause denial of service via malicious image references in Docling Core applications.","url":"https://insights.sbomify.com/CVE-2026-44019/"}