CVE-2026-70479 open-webui CVE debrief

Who should care

Organizations and users of Open WebUI, especially those with sensitive internal addresses or data, should be aware of this vulnerability and take necessary actions to protect themselves. This includes reviewing their current deployment and ensuring that they are running version 0.11.0 or later. Additionally, users should monitor for suspicious activity and restrict access to authenticated users until the patch is applied. Those responsible for vulnerability management and security teams should prioritize patching and verify the effectiveness of compensating controls if immediate patching is not feasible. Operators of Open WebUI should also assess their exposure and implement additional security measures as needed to prevent potential data exposure. This may involve updating their incident response plans and ensuring that their security teams are prepared to respond to potential incidents related to this vulnerability. Furthermore, asset inventory management is crucial to identify and prioritize the patching process for affected systems. Rolling back change windows and tracking sources can also help in managing the remediation process effectively. Monitoring and detection capabilities should be reviewed to ensure they can identify potential exploitation attempts. Overall, a comprehensive approach involving patch management, compensating controls, monitoring, and asset inventory is essential to mitigate the risks associated with this vulnerability. The Open WebUI community and developers should also review the vulnerability details to ensure that similar issues are addressed in the future through secure coding practices and thorough testing of new features. By taking these steps, organizations can reduce the risk of exploitation and protect their sensitive data from potential exposure. It is also recommended to review the official CVE record and NVD details for the latest information on the vulnerability and available patches. Additionally, users should consider implementing a robust vulnerability management program to stay informed about potential vulnerabilities in their software stack and to prioritize remediation efforts based on risk and exposure. This may涉及

Technical summary

The vulnerability in Open WebUI, from version 0.9.6 until 0.11.0, allows an authenticated user to potentially access blocked internal addresses using JavaScript and include data read from those addresses in web-search or RAG output due to insufficient validation of sub-resource requests by the Playwright web loader. This issue is fixed in version 0.11.0. The vulnerability has a CVSS score of 7.7 and is classified as HIGH severity.

Defensive priority

Organizations using Open WebUI should prioritize patching to prevent potential data exposure.

Recommended defensive actions

• Apply the patch from version 0.11.0
• Restrict access to authenticated users
• Monitor for suspicious activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record indicates that Open WebUI, from version 0.9.6 until 0.11.0, with WEB_LOADER_ENGINE=playwright, has a vulnerability where the Playwright web loader validates only the top-level page request and lets sub-resource requests pass unvalidated. This could allow an authenticated user to use JavaScript to reach blocked internal addresses, and returned DOM can include data read from those addresses in web-search or RAG output.

Official resources