← Back
CVE-2026-24009
Unsafe Deserialization in docling-core (CVE-2026-24009)
Summary
vulnerability in docling-core (CVE-2026-24009). Successful exploitation can lead to full system takeover. Exploitable via ``PyYAML``. Mitigation: upgrade to `2.48.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-24009** has been found in docling-core.
Attackers can target a specific entry point like ``PyYAML`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade docling-core to **2.48.4** or later.
If unsure, ask your IT team or search "docling-core CVE-2026-24009" on the vendor's site.
CVE-2026-24009 (docling-core) — CWE-502 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `PyYAML` / `yaml.FullLoader` / `yaml.SafeLoader`
Patched: `2.48.4` — apply immediately
Workaround: Users who cannot immediately upgrade `docling-core` can alternatively ensure that the installed version of `PyYAML` is **5.4 or greater**, which supposedly patches CVE-2020-14343.
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
**unsafe deserialization** (CWE-502) exists in docling-core. Attackers reach the vulnerable code path via ``PyYAML`` without authentication.
📍 Affected scope
docling-core — . Attack surface: `PyYAML` / `yaml.FullLoader` / `yaml.SafeLoader`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.48.4**.
🛡️ Workaround
Workaround: Users who cannot immediately upgrade `docling-core` can alternatively ensure that the installed version of `PyYAML` is **5.4 or greater**, which supposedly patches CVE-2020-14343.
🔍 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
Users who cannot immediately upgrade `docling-core` can alternatively ensure that the installed version of `PyYAML` is **5.4 or greater**, which supposedly patches CVE-2020-14343.パッチが適用されるまでの応急処置として、Users who cannot immediately upgrade `docling-core` can alternatively ensure that the installed version of `PyYAML` is **5.4 or greater**, which supposedly patches CVE-2020-14343. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade docling-core to 2.48.4ステージング環境で 2.48.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
docling-core
[{"type":"ECOSYSTEM","events":[{"introduced":"2.21.0"},{"fixed":"2.48.4"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-24009
- advisory https://github.com/advisories/GHSA-8q59-q68h-6hv4
- advisory https://github.com/advisories/GHSA-vqxf-v2gg-x3hc
- package https://github.com/docling-project/docling-core
- package https://pypi.org/project/docling-core
- web https://github.com/docling-project/docling-core/security/advisories/GHSA-vqxf-v2gg-x3hc
- web https://github.com/docling-project/docling-core/issues/482
- web https://github.com/docling-project/docling-core/commit/3e8d628eeeae50f0f8f239c8c7fea773d065d80c
- web https://github.com/docling-project/docling-core/releases/tag/v2.48.4