docling-graph
Affected
- introduced
0, fixed1.5.1(ecosystem)
Fixed versions
1.5.1
Fix
- Fixed version
1.5.1pip install --upgrade docling-graph==1.5.1
Advisory
Also known as: CVE-2026-44520, PYSEC-2026-2458
docling-graph has SSRF via Missing Internal IP Validation in URLInputHandler
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:
169.254.169.254) to steal IAM credentials127.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 `URLInputHandler` come exclusively from trusted, internal sources, never from user-supplied or external input. There is no safe code-level workaround short of applying the patch, as the vulnerability is in the library itself.
Resources
Medium Basis: The source's own band: MODERATE
0, fixed 1.5.1 (ecosystem)1.5.1
1.5.1pip install --upgrade docling-graph==1.5.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0