← Back
CVE-2026-44520 medium CVSS 5.7

Open Redirect in docling-graph (CVE-2026-44520)

Summary

vulnerability in docling-graph (CVE-2026-44520). Confidential information can be exposed externally. Exploitable via ``URLInputHandler``. Mitigation: upgrade to `1.5.1` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-44520** has been found in docling-graph. Attackers can target a specific entry point like ``URLInputHandler`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: 5.7/10. What to do: upgrade docling-graph to **1.5.1** or later. If unsure, ask your IT team or search "docling-graph CVE-2026-44520" on the vendor's site.
CVE-2026-44520 (docling-graph) — CWE-601 / CVSS v3 5.7 Attack vector: remote (network-reachable) Attack surface: `URLInputHandler` / `URLValidator` / `netloc` / `PipelineConfig.source` Patched: `1.5.1` — apply immediately Workaround: If upgrading is not immediately possible, ensure that **all URLs passed to `URLInputHandler` come exclusively from trusted, internal sources**, never from user-supplied or external input. 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
**A vulnerability** (CWE-601) exists in docling-graph. Attackers reach the vulnerable code path via ``URLInputHandler`` without authentication.
📍 Affected scope
docling-graph — . Attack surface: `URLInputHandler` / `URLValidator` / `netloc` / `PipelineConfig.source`.
🔥 Severity
Severity: Medium (CVSS 5.7/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.5.1**.
🛡️ Workaround
Workaround: If upgrading is not immediately possible, ensure that **all URLs passed to `URLInputHandler` come exclusively from trusted, internal sources**, never from user-supplied or external input.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'docling-graph' .` 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

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

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

  2. 5
    Apply temporary workaround mitigate
    If upgrading is not immediately possible, ensure that **all URLs passed to `URLInputHandler` come exclusively from trusted, internal sources**, never from user-supplied or external input.

    パッチが適用されるまでの応急処置として、If upgrading is not immediately possible, ensure that **all URLs passed to `URLInputHandler` come exclusively from trusted, internal sources**, never from user-supplied or external input. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch
    Upgrade docling-graph to 1.5.1

    ステージング環境で 1.5.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

pip docling-graph
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.5.1"}]}]
PyPI docling-graph
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.5.1"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →