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

Original description

The description as published by the source.

Impact

The URLInputHandler class in docling_graph/core/input/handlers.py makes HTTP requests to user-supplied URLs without validating whether the target resolves to a private, loopback, or link-local IP address. The URLValidator only checks for a valid scheme and non-empty netloc, performing no IP-level validation. Additionally, requests.head() was called with allow_redirects=True, allowing an attacker to redirect requests to internal endpoints via an intermediary URL.

An attacker who can control the --source CLI argument or PipelineConfig.source API parameter can trigger Server-Side Request Forgery (SSRF) to reach:

  • Cloud metadata endpoints (e.g. 169.254.169.254) to steal IAM credentials
  • Internal services on loopback (127.0.0.1) or private network ranges (10.x, 172.16.x, 192.168.x)

This affects deployments where docling-graph processes URLs from untrusted input, such as multi-tenant pipelines or server-side automation.

Patches

The vulnerability is fixed in v1.5.1.

Users should upgrade immediately:

pip install --upgrade docling-graph

The fix adds IP validation via ipaddress and socket.gethostbyname() before any request is made, blocks private/loopback/link-local/reserved addresses, and disables redirect following (allow_redirects=False) with explicit validation of any Location header before following it.

Workarounds

If upgrading is not immediately possible, ensure that **all URLs passed to `URLInputHandle…

Source: NIST National Vulnerability Database 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-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.

📍 Affected scope

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

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. 2
    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. 3
    Apply patch patch 
    Upgrade docling-graph to 1.5.1

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

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

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

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

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