Vulnerability in docling-core (CVE-2026-44019)
Summary
Vulnerability in docling-core (CVE-2026-44019). Confidential information can be exposed externally. Mitigation: upgrade to 2.74.1 or later.
Original description
The description as published by the source.
Docling Core defines core data types and transformations for the document processing application Docling. In versions 2.5.0 and above, prior to 2.74.1, docling-core could allow local file:// image references and accepted inline data: content without a decoded-size limit. In applications that accept untrusted image references, this may allow access to local files readable by the process or excessive memory use from large inline payloads. This issue has been fixed in version 2.74.1.
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-44019 has been found in docling-core.
Confidential information can be exposed externally. CVSS score: 8.1/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-44019" on the vendor's site.
CVE-2026-44019 (docling-core) — CWE-400 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 2.74.1 — apply immediately
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.
A vulnerability (CWE-400) exists in docling-core.
Check the vendor advisory for the affected versions of docling-core.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 2.74.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
grep -r 'docling-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
docling-coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade docling-core to 2.74.1ステージング環境で 2.74.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com