{"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-44022 in the wild and no public exploit code.","fix":"Upgrade docling to 2.91.0 or later.","what":"CVE-2026-44022 is a medium-severity path traversal vulnerability in docling-project docling, published on 24 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-44022 and fix it if it is affected.\n\nWhat it is: CVE-2026-44022 is a medium-severity path traversal vulnerability in docling-project docling, published on 24 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-44022 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- docling (PyPI): affected from 2.73.0; fixed in 2.91.0\n- docling (PyPI): affected from 2.73.0; fixed in 2.91.0\n- docling (PyPI): affected from 2.73.0; fixed in 2.91.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-44022/ (Markdown: https://insights.sbomify.com/CVE-2026-44022/index.md)","id":"CVE-2026-44022","markdown":"https://insights.sbomify.com/CVE-2026-44022/index.md","name":"CVE-2026-44022","record":{"aliases":["GHSA-2j5p-7p5m-cvqr","PYSEC-2026-2145"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python document processing library","requires_auth":"none","summary":"Attackers can read arbitrary files from the file system by crafting malicious LaTeX documents processed by the Docling library.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"docling","vendor":"docling"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem. From 2.73.0 until 2.91.0, he LaTeX backend's handling of \\includegraphics, \\input, and \\include commands lacked path containment validation. Attackers could craft malicious LaTeX documents with path traversal sequences to read arbitrary files from the file system accessible to the process, include sensitive files in the converted document output, or potentially access configuration files, credentials, or other sensitive data This vulnerability is fixed in 2.91.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: Potential Path Traversal via LaTeX \\includegraphics and \\input Commands","id":"CVE-2026-44022","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 Core has unsafe remote filename resolution","id":"CVE-2026-44023"},"packages":[{"ecosystem":"PyPI","fixed":["2.91.0"],"introduced":["2.73.0"],"last_affected":[],"package":"docling","purl":null,"source":"GHSA-2j5p-7p5m-cvqr"},{"ecosystem":"PyPI","fixed":["2.91.0"],"introduced":["2.73.0"],"last_affected":[],"package":"docling","purl":"pkg:pypi/docling","source":"GHSA-2j5p-7p5m-cvqr"},{"ecosystem":"PyPI","fixed":["2.91.0"],"introduced":["2.73.0"],"last_affected":[],"package":"docling","purl":"pkg:pypi/docling","source":"PYSEC-2026-2145"}],"prev":{"headline":"Docling: Unsafe XML Entity Expansion in USPTO Patent Backend","id":"CVE-2026-44020"},"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.5,"headline":"Docling: Unsafe XML Entity Expansion in USPTO Patent Backend","id":"CVE-2026-44020","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-25","vendors":["docling-project"]},"summary":"Attackers can read arbitrary files from the file system by crafting malicious LaTeX documents processed by the Docling library.","url":"https://insights.sbomify.com/CVE-2026-44022/"}