open-webui Open WebUI up to 0.6.36 server-side request forgery

Summaryinfo

A vulnerability identified as critical has been detected in open-webui Open WebUI up to 0.6.36. This issue affects some unknown processing. Performing a manipulation results in server-side request forgery. This vulnerability is identified as CVE-2025-65958. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in open-webui Open WebUI up to 0.6.36. This affects some unknown functionality. The manipulation with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to 0.6.37, a Server-Side Request Forgery (SSRF) vulnerability in Open WebUI allows any authenticated user to force the server to make HTTP requests to arbitrary URLs. This can be exploited to access cloud metadata endpoints (AWS/GCP/Azure), scan internal networks, access internal services behind firewalls, and exfiltrate sensitive information. No special permissions beyond basic authentication are required. This vulnerability is fixed in 0.6.37.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2025-65958 since 11/18/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 0.6.37 eliminates this vulnerability. Applying the patch 02238d3113e966c353fce18f1b65117380896774 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• open-webui

Name

• Open WebUI

Version

• 0.6.0
• 0.6.1
• 0.6.2
• 0.6.3
• 0.6.4
• 0.6.5
• 0.6.6
• 0.6.7
• 0.6.8
• 0.6.9
• 0.6.10
• 0.6.11
• 0.6.12
• 0.6.13
• 0.6.14
• 0.6.15
• 0.6.16
• 0.6.17
• 0.6.18
• 0.6.19
• 0.6.20
• 0.6.21
• 0.6.22
• 0.6.23
• 0.6.24
• 0.6.25
• 0.6.26
• 0.6.27
• 0.6.28
• 0.6.29
• 0.6.30
• 0.6.31
• 0.6.32
• 0.6.33
• 0.6.34
• 0.6.35
• 0.6.36

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion