PYSEC-2026-2145

Vulnerability from pysec - Published: 2026-06-24 18:17 - Updated: 2026-07-13 05:48
VLAI
Details

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.

Impacted products
Name purl
docling pkg:pypi/docling

{
  "affected": [
    {
      "ecosystem_specific": {},
      "package": {
        "ecosystem": "PyPI",
        "name": "docling",
        "purl": "pkg:pypi/docling"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.73.0"
            },
            {
              "fixed": "2.91.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "2.73.0",
        "2.73.1",
        "2.74.0",
        "2.75.0",
        "2.76.0",
        "2.77.0",
        "2.78.0",
        "2.79.0",
        "2.80.0",
        "2.81.0",
        "2.82.0",
        "2.83.0",
        "2.84.0",
        "2.85.0",
        "2.86.0",
        "2.87.0",
        "2.88.0",
        "2.89.0",
        "2.90.0"
      ]
    }
  ],
  "aliases": [
    "CVE-2026-44022",
    "GHSA-2j5p-7p5m-cvqr"
  ],
  "details": "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\u0027s 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.",
  "id": "PYSEC-2026-2145",
  "modified": "2026-07-13T05:48:35.587732Z",
  "published": "2026-06-24T18:17:17.593Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://github.com/docling-project/docling/releases/tag/v2.91.0"
    },
    {
      "type": "FIX",
      "url": "https://github.com/docling-project/docling/security/advisories/GHSA-2j5p-7p5m-cvqr"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…