CVE-2026-70486

This vulnerability chains three distinct application layers—a file preview feature, an iframe sandbox policy with overly permissive flags, and localStorage-based session management—into an account takeover vector that should concern you even if the EPSS score looks reassuring. The core mechanism: Open WebUI's file preview functionality uses an iframe with `allow-same-origin` and `allow-scripts` flags. The first flag grants the iframe access to the parent document's origin, including its localStorage. The second allows the iframe to execute JavaScript. Together, they mean any file preview can execute scripts in the application's origin and read authentication tokens stored in localStorage. With those tokens, an attacker can impersonate the user and, given Open WebUI's capability for server-side code execution, potentially escalate to arbitrary command execution on the host. The terminal server prerequisite complicates exploitation but doesn't eliminate it. If your deployment runs the terminal server integration, treat this as exploitable until proven otherwise. The EPSS of 0.00374 reflects the absence of in-the-wild exploitation evidence on a freshly disclosed CVE—it says nothing about your actual exposure and will update as the vulnerability ages. The fix complexity matters for your prioritization. If this was resolved through a single sandbox flag change, the vulnerability was a configuration error rather than an architectural inevitability—but that classification should make you more concerned, not less. Configuration errors are trivial to replicate, and this specific pattern of iframe sandbox misconfiguration has appeared across dozens of applications over the past decade. Each instance gets individually fixed, institutional memory doesn't transfer, and the next development team building file previews in a new platform makes the same mistake. The recurrence is the signal: this isn't a one-off flaw, it's an ecological failure mode. What you should check: confirm your Open WebUI version and whether the terminal server integration is enabled. Review your iframe sandbox policies if you've extended the platform with custom integrations—any that use both same-origin and script permissions deserve scrutiny. Consider moving session tokens to httpOnly cookies if the application architecture supports it; the localStorage dependency is what makes this vulnerability severe. Finally, treat trivial-seeming CVEs with catastrophic composition paths as higher priority than their scores suggest, because the fix may be easy but the organizational inertia to apply it is not.

Reviewed through automated stages and approved by a human before publication.