dbcve.org
Open RedirectWeakness · CWE-601

CVE-2026-44520

MEDIUM · 5.7 CVSS v3.1 Published 2026-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Docling-Graph turns documents into validated Pydantic objects, then builds a directed knowledge graph with explicit semantic relationships. Prior to 1.5.1, 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). This vulnerability is fixed in 1.5.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The URLInputHandler class in docling-graph versions prior to 1.5.1 makes HTTP requests to user-supplied URLs without validating whether the target resolves to private, loopback, or link-local IP addresses, enabling Server-Side Request Forgery (SSRF). Additionally, requests.head() was called with allow_redirects=True, allowing attackers to redirect requests to internal endpoints via an intermediary URL.

MitigationUpgrade to docling-graph version 1.5.1 or later, which implements proper IP-level validation to reject requests to private/internal addresses and properly handles redirect scenarios.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed docling-graph version
    Run `pip show docling-graph` or `pip list | grep docling-graph` to see the installed version number
    Affected if Version is lower than 1.5.1 (e.g., 1.5.0, 1.4.x, 1.3.x, etc.)
  2. Locate URLInputHandler usage
    Search project code for imports or references to `URLInputHandler` from docling_graph, or check if the application accepts URLs as input from users or external sources
    Affected if URLInputHandler class is imported and used to process user-supplied URLs
  3. Verify HTTP request behavior
    Inspect the source code of URLInputHandler (typically in docling_graph library path) to confirm it uses requests.head() or requests.get() without IP validation for private addresses
    Affected if The handler makes HTTP requests to arbitrary URLs without validating target IP addresses against private/loopback/link-local ranges, and uses allow_redirects=True
  4. Test for SSRF exposure
    If URLInputHandler processes user input, provide a test URL like http://127.0.0.1:port or http://localhost to see if the application attempts to connect
    Affected if The application successfully makes HTTP requests to localhost or private IP addresses supplied by user input

You are affected if docling-graph version is below 1.5.1 AND your application uses URLInputHandler to process untrusted URLs without additional IP validation layer.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to docling-graph version 1.5.1 or later, which implements proper IP-level validation to reject requests to private/internal addresses and properly handles redirect scenarios.

Recommended fix High confidence

1.5.1

  1. Verify the current installed version of docling-graph by running: pip show docling-graph or pip list | grep docling
  2. Upgrade to version 1.5.1 or later by running: pip install --upgrade docling-graph
  3. Alternatively, if using a specific version requirement: pip install docling-graph>=1.5.1
  4. After upgrading, verify the new version is installed: pip show docling-graph
  5. If using docling-graph in a project, ensure the version is updated in any requirements.txt or pyproject.toml files
Caveat No breaking changes mentioned in the vulnerability description

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44520 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44520 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data