Vulnerability in docling (CVE-2026-105743)
Summary
Vulnerability in docling (CVE-2026-105743). Risk of unauthorized operations or information disclosure. Exploitable via validate_url_safety. Mitigation: upgrade to 2.132.0 or later.
Original description
The description as published by the source.
Summary
When remote fetching is enabled (enable_remote_fetch=True, together with fetch_images=True or HTML render_page=True), docling's protection against requests to private and loopback addresses can be bypassed.
- The URL check resolves the host name once, to a single IPv4 address. The HTTP request then resolves it again. A name that returns a public A record together with an internal AAAA record, or one that changes its answer between the two lookups (DNS rebinding), reaches internal addresses.
- The check and the HTTP request parse the URL differently. With a backslash in the authority, such as
http://127.0.0.1:8080\@1.1.1.1/x.png, the check validates1.1.1.1while the HTTP client connects to127.0.0.1:8080. - In HTML browser-rendering mode (
render_page=True), requests made by the page are allowed for anyhttp(s)URL without an IP check.
Details
validate_url_safetyindocling/backend/utils/image_resource_loader.pycallssocket.gethostbyname(), which returns one IPv4 address. It checks that address and then passes the original URL string torequests, which parses it again with urllib3 and resolves the name independently throughgetaddrinfo.urllib.parsetreats a backslash in the authority as part of the host section, while urllib3 ends the authority there, so the two can pick different hosts. This loader is shared by the HTML, Markdown, AsciiDoc, OpenDocument and JATS backends.docling/backend/html_backend.pyroutes browser re…
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-105743 has been found in docling.
Attackers can target a specific entry point like validate_url_safety over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.0/10.
What to do: upgrade docling to 2.132.0 or later.
If unsure, ask your IT team or search "docling CVE-2026-105743" on the vendor's site.
CVE-2026-105743 (docling) — CWE-367 / CVSS v3 4.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: validate_url_safety / requests / getaddrinfo / urllib.parse
Patched: 2.132.0 — 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-367) exists in docling. Attackers reach the vulnerable code path via validate_url_safety without authentication.
Check the vendor advisory for the affected versions of docling. Attack surface: validate_url_safety / requests / getaddrinfo / urllib.parse.
Severity: Medium (CVSS 4.0/10). Risk of unauthorized operations or information disclosure.
Update to 2.132.0.
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' . 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' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
doclingを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade docling to 2.132.0ステージング環境で 2.132.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。