CVE-2026-54020
Received Received - Intake

SSRF in Open WebUI Prior to 0.11.0

Vulnerability report for CVE-2026-54020, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-04

Last updated on: 2026-08-04

Assigner: GitHub, Inc.

Description

Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. Prior to 0.11.0, Open WebUI resolved a hostname during URL validation and rejected private, loopback, and link-local addresses, but the HTTP clients resolved the hostname again at connection time. An authenticated attacker who controlled authoritative DNS for a submitted hostname could answer with a public address during validation and an internal one during connection, reaching cloud metadata, loopback admin APIs, or internal services through URL ingest, chat image_url fetches, image editing, or OAuth profile-picture fetches, with most paths returning the response to the attacker and the OAuth path forwarding the OAuth access token. This issue is fixed in 0.11.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-04
Last Modified
2026-08-04
Generated
2026-08-05
AI Q&A
2026-08-05
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
open_webui open_webui to 0.11.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-367 The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

Open WebUI before 0.11.0 had a flaw in hostname validation for URLs. It checked if a hostname was private or internal during validation but did not enforce this restriction when making the actual HTTP connection. An attacker controlling DNS could provide a public IP during validation and an internal IP during connection, bypassing restrictions and accessing internal services or metadata.

Detection Guidance

Detecting this vulnerability requires checking if your Open WebUI instance is running a version prior to 0.11.0. Use the command: curl -s http://localhost:8080/api/version | grep version. If the version is less than 0.11.0, the system is vulnerable.

Impact Analysis

If you use Open WebUI before 0.11.0, an attacker could trick the system into connecting to internal services or cloud metadata by submitting a malicious URL. This could lead to unauthorized access to sensitive data, exposure of OAuth tokens, or interaction with internal APIs.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, which may violate GDPR's data protection principles or HIPAA's security requirements for protected health information. Organizations using vulnerable versions risk non-compliance due to potential data breaches or unauthorized data exposure.

Mitigation Strategies

Upgrade Open WebUI to version 0.11.0 or later immediately. This version fixes the hostname resolution issue during URL validation and connection time.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-54020. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart