CVE-2026-26193 is a stored cross-site scripting vulnerability in Open WebUI prior to version 0.6.44. The issue arises because manually modified chat history can set the embeds property on a response message, and that embed content is rendered in an iFrame from the vulnerable code path in src/lib/components/chat/Messages/ResponseMessage.svelte. The iframe is configured with both allow-scripts and allow-same-origin, and this behavior ignores the "iframe Sandbox Allow Same Origin" configuration. As a result, attacker-controlled embed content, including data:text/html or javascript: payloads, can execute when the affected chat is viewed. The issue is stored/persistent because the malicious payload is saved in chat content and also propagates through the application's shared chat format, producing a shareable link that can deliver the payload to other users on the same instance.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
embeds containing data:text/html or javascript: is relevant. Reducing exposure of administrative sessions to untrusted shared chats and avoiding opening user-supplied shared links can also reduce risk until the upgrade is applied.Patch, then assume compromise.
allowSameOrigin is no longer always enabled and instead follows the intended IFRAME_SANDBOX_ALLOW_SAME_ORIGIN control. In addition to upgrading, review stored chats for malicious embeds content, especially payloads containing data:text/html or javascript: URIs, and remove any weaponized chats or shared links already present in the instance.No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.