Sign in Sign up
JA · EN · FR
SecPulse
Categories
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.

Original description

The description as published by the source.

Impact

In versions >= 1.5.0, < 2.74.1, docling-core did not sufficiently restrict remote request destinations and could resolve a server-provided Content-Disposition to a local path in an unsafe manner.

In applications that accept untrusted URLs, this could allow SSRF attacks targeting local files outside the user-defined cache directory.

Patches

Patched in docling-core 2.74.1.
The fix adds stricter validation for remote destinations and normalizes server-provided filenames before use.

Users should upgrade to:

  • docling-core >= 2.74.1

Workarounds

If upgrading is not immediately possible, avoid passing untrusted URLs into remote fetch functionality.

References

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

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

Check the vendor advisory for the affected versions of 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

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'docling-core' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で docling-core を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply 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. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade docling-core to 2.74.1

    ステージング環境で 2.74.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

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"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details