Server-Side Request Forgery (SSRF) Affecting open-webui package, versions <0.9.2-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.04% (12th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Server-Side Request Forgery (SSRF) vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CHAINGUARDLATEST-OPENWEBUI-16439034
  • published7 May 2026
  • disclosed24 Apr 2026

Introduced: 24 Apr 2026

NewCVE-2026-41481  (opens in a new tab)
CWE-918  (opens in a new tab)

How to fix?

Upgrade Chainguard open-webui to version 0.9.2-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream open-webui package and not the open-webui package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

LangChain is a framework for building agents and LLM-powered applications. Prior to langchain-text-splitters 1.1.2, HTMLHeaderTextSplitter.split_text_from_url() validated the initial URL using validate_safe_url() but then performed the fetch with requests.get() with redirects enabled (the default). Because redirect targets were not revalidated, a URL pointing to an attacker-controlled server could redirect to internal, localhost, or cloud metadata endpoints, bypassing SSRF protections. The response body is parsed and returned as Document objects to the calling application code. Whether this constitutes a data exfiltration path depends on the application: if it exposes Document contents (or derivatives) back to the requester who supplied the URL, sensitive data from internal endpoints could be leaked. Applications that store or process Documents internally without returning raw content to the requester are not directly exposed to data exfiltration through this issue. This vulnerability is fixed in 1.1.2.