CVE-2026-105744

waiting for further signalsZero needs more public information before it can validate it.

GHSA-x3q2-h9hx-4r4j ↗EUVD-2026-92804 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+2.0dkevAttacks confirmed in the real world.
docling-project docling >= 2.94.0, < 2.132.0
fixed in 2.132.0
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-683, permanent identifier
pkg:pypi/docling
pkg:pypi/docling-slim
13d 07h 24msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0dpublic poc+2.0dwaiting for further signals
0
+1d

description

Docling and docling-slim can process attacker-controlled LaTeX with Tectonic in a way that permits access to files readable or writable by the conversion process. This requires explicitly enabling the Tectonic TikZ renderer and having Tectonic available; shell command execution is additionally possible if shell escape is enabled.

mitigation

Upgrade docling or docling-slim to version 2.132.0 or later. Until then, do not use Tectonic TikZ rendering for untrusted input, disable shell escape, and isolate conversions from host files and networks.

fixed in 2.132.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.34%26th percentile
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-05 21:26Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+2.0d
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-05 21:26Z
    cve_org: trigger signal, started the run
  2. 2026-10-07 20:42Z

this entry in the feed

GET /api/v1/feed/CVE-2026-105744

{
  "etk_id": "ETK-2026-683",
  "cve_id": "CVE-2026-105744",
  "display_id": "CVE-2026-105744",
  "ghsa_id": "GHSA-x3q2-h9hx-4r4j",
  "euvd_id": "EUVD-2026-92804",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Arbitrary file access in docling Tectonic TikZ rendering",
  "summary": "Docling and docling-slim can process attacker-controlled LaTeX with Tectonic in a way that permits access to files readable or writable by the conversion process. This requires explicitly enabling the Tectonic TikZ renderer and having Tectonic available; shell command execution is additionally possible if shell escape is enabled.",
  "mitigation": "Upgrade docling or docling-slim to version 2.132.0 or later. Until then, do not use Tectonic TikZ rendering for untrusted input, disable shell escape, and isolate conversions from host files and networks.",
  "vendor": "docling-project",
  "product": "docling",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.94.0, < 2.132.0"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "2.132.0"
      ],
      "package_name": "docling",
      "purl": "pkg:pypi/docling"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.94.0, < 2.132.0"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        "2.132.0"
      ],
      "package_name": "docling-slim",
      "purl": "pkg:pypi/docling-slim"
    }
  ],
  "cwes": [
    22
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H",
  "epss_score": 0.0034,
  "epss_percentile": 0.2652,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.198475983333333,
  "t0_at": "2026-10-05T21:26:56.685000+00:00",
  "signals": {
    "public_poc": {
      "at": "2026-10-07T20:42:05+00:00",
      "days": 1.968846238425926,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T21:26:56.685000+00:00",
      "url": "https://github.com/advisories/GHSA-x3q2-h9hx-4r4j"
    },
    "trigger_signal": {
      "at": "2026-10-05T21:26:56.685000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-05T21:26:56.685000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-105744"
    }
  }
}

published 2026-10-05 22:02Z
last change 2026-10-21 05:31Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.