Incident Score: Analysis & Impact (OPE1767733551)
The details regarding individual company incidents & reports gives you full view from every side.
Rankiteo Score Impact Analysis
Key Highlights From The Incident Analysis
- Timeline of Open WebUI's Vulnerability and lateral movement inside company's environment.
- Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
- How Rankiteo’s incident engine converts technical details into a normalized incident score.
- How this cyber incident impacts Open WebUI Rankiteo cyber scoring and cyber rating.
- Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.
Full Incident Analysis Transcript
In this Rankiteo incident briefing, we review the Open WebUI breach identified under incident ID OPE1767733551.
The analysis begins with a detailed overview of Open WebUI's information like the linkedin page: https://www.linkedin.com/company/open-webui, the number of followers: 1566, the industry type: Software Development and the number of employees: 3 employees
After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 749 and after the incident was 746 with a difference of -3 which is could be a good indicator of the severity and impact of the incident.
In the next step of the video, we will analyze in more details the incident and the impact it had on Open WebUI and their customers.
Open WebUI recently reported "CVE-2025-64496: Code Injection Flaw in Open WebUI Direct Connection Features", a noteworthy cybersecurity incident.
Open WebUI carried CVE-2025-64496, a high-severity code injection flaw in Direct Connection features.
The disruption is felt across the environment, affecting Open WebUI backend servers, and exposing Tokens, account credentials.
In response, moved swiftly to contain the threat with measures like Patch v0.6.35 released to block SSE execution from Direct Connection servers, and began remediation that includes Middleware protections added, users advised to restrict Direct Connections to vetted services, and stakeholders are being briefed through Public disclosure, patch release, user advisories.
The case underscores how Disclosed, patch available, teams are taking away lessons such as Treat connections to external AI servers like third-party code; limit Direct Connections to vetted services; restrict workspace.tools permissions to essential users, and recommending next steps like Patch to Open WebUI v0.6.35 or newer, Restrict Direct Connections to properly vetted services and Limit workspace.tools permissions to essential users, with advisories going out to stakeholders covering Users urged to apply patch v0.6.35 and restrict Direct Connections.
Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.
The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.
MITRE ATT&CK® Correlation Analysis
Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Exploit Public-Facing Application (T1190) with high confidence (90%), supported by evidence indicating high-severity code injection flaw in Open WebUI Direct Connection features and User Execution: Malicious Link (T1204.001) with moderate to high confidence (80%), supported by evidence indicating exploitation requires victims to add a malicious model URL via social engineering. Under the Execution tactic, the analysis identified JavaScript (T1059.007) with high confidence (90%), supported by evidence indicating attackers execute arbitrary JavaScript via Server-Sent Event (SSE) execute events and Exploitation for Client Execution (T1203) with moderate to high confidence (80%), supported by evidence indicating code injection flaw enables remote code execution (RCE) via Functions API chaining. Under the Credential Access tactic, the analysis identified Steal Application Access Token (T1528) with high confidence (90%), supported by evidence indicating account takeover through token theft via malicious SSE execute events and Credentials In Files (T1552.001) with moderate to high confidence (70%), supported by evidence indicating data compromised includes tokens, account credentials. Under the Privilege Escalation tactic, the analysis identified Exploitation for Privilege Escalation (T1068) with moderate to high confidence (80%), supported by evidence indicating rCE on backend server via Functions API chaining after initial access. Under the Defense Evasion tactic, the analysis identified Valid Accounts (T1078) with moderate to high confidence (70%), supported by evidence indicating account takeover enables use of legitimate credentials for further access and Exploitation for Defense Evasion (T1211) with moderate confidence (60%), supported by evidence indicating trust boundary failure between untrusted model servers and trusted browser context. Under the Impact tactic, the analysis identified Endpoint Denial of Service (T1499.004) with moderate confidence (50%), supported by evidence indicating potential RCE on backend servers could disrupt operations and Account Access Removal (T1531) with moderate to high confidence (70%), supported by evidence indicating account takeover via token theft and credential compromise. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.
Sources & References
- Open WebUI Rankiteo Cyber Incident Details: https://www.rankiteo.com/company/open-webui/incident/OPE1767733551
- Open WebUI CyberSecurity Rating page: https://www.rankiteo.com/company/open-webui
- Open WebUI Rankiteo Cyber Incident Blog Article: https://blog.rankiteo.com/ope1767733551-vulnerability-january-2026/
- Open WebUI CyberSecurity Score History: https://www.rankiteo.com/company/open-webui/history
- Open WebUI CyberSecurity Incident Source: https://www.techradar.com/pro/security/this-webui-vulnerability-allows-remote-code-execution-heres-how-to-stay-safe
- Rankiteo A.I CyberSecurity Rating methodology: https://www.rankiteo.com/Images/rankiteo_algo.pdf
- Rankiteo TPRM Scoring methodology: https://static.rankiteo.com/model/rankiteo_tprm_methodology.pdf