<Vulnerability name="CVE-2026-44022">
    <DocumentDistribution xml:lang="en">Copyright © 2012 Red Hat, Inc. All rights reserved.</DocumentDistribution>
    <ThreatSeverity>Moderate</ThreatSeverity>
    <PublicDate>2026-06-24T17:47:25</PublicDate>
    <Bugzilla id="2492379" url="https://bugzilla.redhat.com/show_bug.cgi?id=2492379" xml:lang="en:us">
docling: Docling: Information disclosure via path traversal in LaTeX backend
    </Bugzilla>
    <CVSS3 status="draft">
        <CVSS3BaseScore>5.5</CVSS3BaseScore>
        <CVSS3ScoringVector>CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N</CVSS3ScoringVector>
    </CVSS3>
    <CWE>CWE-22</CWE>
    <Details xml:lang="en:us" source="Mitre">
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.
    </Details>
    <Details xml:lang="en:us" source="Red Hat">
A flaw was found in Docling, a tool for document processing. The LaTeX backend, responsible for handling commands like \includegraphics, \input, and \include, lacked proper validation for file paths. This vulnerability allows an attacker to craft a malicious LaTeX document containing path traversal sequences. When processed, this could enable the attacker to read arbitrary files from the system, include sensitive files in the converted document output, and potentially access confidential information such as configuration files or credentials.
    </Details>
    <Statement xml:lang="en:us">
This Moderate impact flaw in Docling's LaTeX backend allows an attacker to read arbitrary files from the system. By crafting a malicious LaTeX document with path traversal sequences, an attacker could exploit this vulnerability when a user processes the document, potentially leading to the disclosure of sensitive information such as configuration files or credentials. This issue primarily affects instances where Docling is used to process untrusted LaTeX content, such as within Red Hat OpenShift AI.
    </Statement>
    <Mitigation xml:lang="en:us">
To mitigate this vulnerability, avoid processing untrusted LaTeX documents with Docling. If processing untrusted documents is unavoidable, ensure that Docling operates within a sandboxed environment with strictly limited file system access to prevent unauthorized file reads.
    </Mitigation>
    <PackageState cpe="cpe:/a:redhat:openshift_ai">
        <ProductName>Red Hat OpenShift AI (RHOAI)</ProductName>
        <FixState>Fix deferred</FixState>
        <PackageName>rhoai/odh-autorag-rhel9</PackageName>
    </PackageState>
    <References xml:lang="en:us">
https://www.cve.org/CVERecord?id=CVE-2026-44022
https://nvd.nist.gov/vuln/detail/CVE-2026-44022
https://github.com/docling-project/docling/releases/tag/v2.91.0
https://github.com/docling-project/docling/security/advisories/GHSA-2j5p-7p5m-cvqr
    </References>
</Vulnerability>