← Back
CVE-2026-44023
high
CVSS 8.6
Path Traversal in docling-core (CVE-2026-44023)
Summary
path traversal in docling-core (CVE-2026-44023). Confidential information can be exposed externally. Mitigation: upgrade to `2.74.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44023** has been found in docling-core.
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: upgrade docling-core to **2.74.1** or later.
If unsure, ask your IT team or search "docling-core CVE-2026-44023" on the vendor's site.
CVE-2026-44023 (docling-core) — CWE-22 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `2.74.1` — apply immediately
Workaround: If upgrading is not immediately possible, avoid passing untrusted URLs into remote fetch functionality.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in docling-core.
📍 Affected scope
docling-core — .
🔥 Severity
Severity: High (CVSS 8.6/10). Confidential information can be exposed externally
🔧 How to fix
Update to **2.74.1**.
🛡️ Workaround
Workaround: If upgrading is not immediately possible, avoid passing untrusted URLs into remote fetch functionality.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'docling-core' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'docling-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `docling-core` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
If upgrading is not immediately possible, avoid passing untrusted URLs into remote fetch functionality.パッチが適用されるまでの応急処置として、If upgrading is not immediately possible, avoid passing untrusted URLs into remote fetch functionality. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade docling-core to 2.74.1ステージング環境で 2.74.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
docling-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.74.1"}]}]
PyPI
docling-core
[{"type":"ECOSYSTEM","events":[{"introduced":"1.5.0"},{"fixed":"2.74.1"}]}]