Open WebUI A.I CyberSecurity Scoring
Open WebUI
Company Information
Website:https://openwebui.com
Employees number:2
Number of followers:762,093
NAICS:5112
Industry Type:Software Development
Homepage:openwebui.com
Open WebUI Risk Score (AI oriented)
Between 700 and 749
Open WebUISoftware Development
Updated:
12/05/2026
12/05/2026
744/1000
Moderate
Ba
Open WebUI Global Score (TPRM)
xxxx
Open WebUISoftware Development
Score locked

Open WebUIModerate
Current Score
744Ba (MODERATE)
01000
2 incidents
-4.5 avg impact
Incident timeline with MITRE ATT&CK tactics, techniques, and mitigations.
AUGUST 2026
745
JULY 2026
745
JUNE 2026
745
MAY 2026
744
APRIL 2026
744
MARCH 2026
749
Vulnerability
01 Mar 2026 • Open WebUI
Open WebUI: Open WebUI File Upload Vulnerability Enables One-Click RCE Attacks
Critical Unpatched XSS Flaw in Open WebUI Enables 1-Click RCE and Account Takeover
743
CRITICAL-6
OPE1778588739
Critical Unpatched XSS Flaw in Open WebUI Enables 1-Click RCE and Account Takeover
Security researchers have disclosed a severe stored Cross-Site Scripting (XSS) vulnerability in Open WebUI, allowing attackers to achieve remote code execution (RCE) or full account hijacking with minimal user interaction. The flaw, discovered by researcher Metin Yunus Kandemir, stems from improper validation of profile image uploads, specifically when handling base64-encoded SVG files.
### How the Attack Works
The vulnerability exploits Open WebUI’s backend routing, where the system fails to enforce strict file-type restrictions. Attackers can embed malicious JavaScript in an SVG file using the `data:image/svg+xml;base64` format. When uploaded as a profile picture, the server processes and renders the file inline, executing the embedded code in the victim’s browser.
The attack chain unfolds in two scenarios:
1. Administrator/Privileged User Compromise – If the victim has elevated access, the payload silently calls Open WebUI’s API to create a malicious tool, injecting a reverse shell for full RCE.
2. Standard User Account Takeover – For non-privileged users, the payload extracts local storage tokens and chat logs, transmitting them to an attacker-controlled server.
Key targeted API endpoints include:
- `/api/v1/tools/create` (RCE payload delivery)
- `/api/v1/chats/all` (chat history extraction)
- `/api/v1/users/search` (user enumeration)
- `/api/v1/users/[user_id]/profile/image` (malicious SVG execution)
### Disclosure and Current Status
Researchers privately reported the issue to Open WebUI maintainers in March, but the report was closed as a duplicate of a non-public advisory, with no official acknowledgment. Frustrated by the lack of response, researchers publicly disclosed the flaw to warn users.
As of version 0.7.2, the vulnerability remains unpatched. Until an official fix is released, organizations using Open WebUI are exposed to phishing-driven attacks, where a single click on a malicious link could trigger exploitation. The flaw is particularly dangerous in enterprise environments, where compromised admin accounts could lead to widespread system breaches.
INCIDENT DETAILS -
TYPE
IMPACT
DATA BREACH
REFERENCES
FEBRUARY 2026
749
JANUARY 2026
751
Vulnerability
06 Jan 2026 • Open WebUI
Open WebUI: This WebUI vulnerability allows remote code execution - here's how to stay safe
CVE-2025-64496: Code Injection Flaw in Open WebUI Direct Connection Features
748
CRITICAL-3
OPE1767733551
High-Severity Vulnerability in Open WebUI Enables Account Takeover and RCE
A high-severity code injection flaw, tracked as CVE-2025-64496 (CVSS 8.0), was discovered in Open WebUI, an open-source, self-hosted interface for AI language models. The vulnerability, disclosed in October 2025 by Cato CTRL Senior Security Researcher Vitaly Simonovich, affects versions 0.6.34 and earlier and resides in the Direct Connection feature.
The flaw allows attackers to execute arbitrary JavaScript via Server-Sent Event (SSE) execute events, enabling account takeover through token theft. When chained with the Functions API, the exploit can escalate to remote code execution (RCE) on the backend server.
Exploitation requires victims to enable Direct Connections (disabled by default) and add a malicious model URL, which can be achieved through social engineering. The patch, version 0.6.35, introduces middleware protections to block malicious SSE execution from Direct Connection servers.
Researchers recommend restricting Direct Connections to vetted services, limiting workspace.tools permissions to essential users, and monitoring for suspicious tool creations. The vulnerability highlights a trust boundary failure between untrusted model servers and a trusted browser context.
INCIDENT DETAILS -
TYPE
IMPACT
DATA BREACH
REFERENCES
DECEMBER 2025
751
NOVEMBER 2025
751
OCTOBER 2025
751
SEPTEMBER 2025
751
Frequently Asked Questions
?
What is the current A.I Rankiteo Cyber Score for Open WebUI ??
What was Open WebUI's A.I Rankiteo Cyber Score in July 2026 ??
What was Open WebUI's A.I Rankiteo Cyber Score in June 2026 ??
What was Open WebUI's A.I Rankiteo Cyber Score in May 2026 ??
What was Open WebUI's A.I Rankiteo Cyber Score in April 2026 ??
What was Open WebUI's A.I Rankiteo Cyber Score in March 2026 ??
What was Open WebUI's A.I Rankiteo Cyber Score in February 2026 ??
What was Open WebUI's A.I Rankiteo Cyber Score in January 2026 ??
What was Open WebUI's A.I Rankiteo Cyber Score in December 2025 ??
What was Open WebUI's A.I Rankiteo Cyber Score in November 2025 ??
What was Open WebUI's A.I Rankiteo Cyber Score in October 2025 ??
What was Open WebUI's A.I Rankiteo Cyber Score in September 2025 ??
What is the average per-incident point impact on Open WebUI's A.I Rankiteo Cyber Score over the past 12 months ??
Where can I access detailed records of all cyber incidents associated with Open WebUI ??
Where can I find a summary of the A.I Rankiteo Risk Scoring methodology ??
Where can I view Open WebUI's profile page on Rankiteo ??
How accurate is the A.I Rankiteo Risk Scoring methodology ?