CVE-2026-26192

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:github_m, epss
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Open WebUI vulnerable to Stored XSS via iFrame in citations model

Summary

Manually modifying chat history allows setting the html property within document metadata. This causes the frontend to enter a code path that treats document contents as HTML, and render them in an iFrame when the citation is previewed. This allows stored XSS via a weaponised document payload in a chat. The payload also executes when the citation is viewed on a shared chat.

Details

The vulnerability stems from how iFrame are implemented here: https://github.com/open-webui/open-webui/blob/6f1486ffd0cb288d0e21f41845361924e0d742b3/src/lib/components/chat/Messages/Citations/CitationModal.svelte#L163-L170 The html attribute can be controlled by a user who manually edits the chat history. Since allow-scripts and allow-same-origin are harcoded here the sandboxing offers essentially no protection.

PoC

Create an arbitrary chat with a file upload attached:

Edit the response

Before saving, configure the browser to use an HTTP proxy tool (Burp/Caido/ZAP) and intercept the save request. Find the object within the history and then messages objects (not the messages array) that contains the document source.

Add html: true to metadata, update the document to an XSS payload, and forward the request.

Observe the payload is rendered in the iFrame and the javascript executes.

The payload also executes when viewed from a shared version of the chat.

Impact

Any user can create a weaponised chat that can be shared and subsequently used to target other users.

Low privilege users are at risk of having their session taken over by a payload that reads their token from local storage and exfiltrates it to an attacker controlled server.

Admins are at risk of exposing the server to RCE via same chain described in https://github.com/advisories/GHSA-w7xj-8fx7-wfch.

Caveats

The victim must expand the sources and click the document containing the payload to trigger this issue.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity73% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.3%
EPSS %ILE
22nd
KEV
Not listed

Published

July 7, 2026

Last Modified

July 7, 2026

Vendor Advisories for CVE-2026-26192(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
open-webui0.1.124 ... 0.6.9 (135 versions)
  • every version up to 0.7.0: fixed in 0.7.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 140 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:11 UTCEPSS rescore
  4. 2026-10-07 23:47 UTCEPSS rescore
  5. 2026-10-06 15:17 UTCEPSS rescore
  6. 2026-10-05 17:42 UTCEPSS rescore
  7. 2026-10-04 23:21 UTCEPSS rescore
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-28 13:37 UTCEG score recompute
  13. 2026-09-26 15:58 UTCEPSS rescore
  14. 2026-09-26 00:26 UTCEPSS rescore
  15. 2026-09-23 06:17 UTCEG score recompute
  16. 2026-09-20 20:15 UTCEPSS rescore
  17. 2026-09-20 20:15 UTCEPSS rescore
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-18 19:27 UTCEPSS rescore
  20. 2026-09-18 05:50 UTCEG score recompute
  21. 2026-09-16 14:07 UTCEPSS rescore
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-13 23:53 UTCEG score recompute
  24. 2026-09-13 16:47 UTCEPSS rescore
  25. 2026-09-12 16:45 UTCEG score recompute
Show 75 more
  1. 2026-09-12 15:01 UTCEPSS rescore
  2. 2026-09-12 03:43 UTCEG score recompute
  3. 2026-09-11 14:52 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 14:08 UTCEG score recompute
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-05 22:54 UTCEG score recompute
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:11 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 20:41 UTCEG score recompute
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 07:43 UTCEG score recompute
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 21:55 UTCEG score recompute
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-27 01:58 UTCEG score recompute
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-26 12:59 UTCEG score recompute
  25. 2026-08-25 13:48 UTCEPSS rescore
  26. 2026-08-24 23:48 UTCEG score recompute
  27. 2026-08-24 10:50 UTCEG score recompute
  28. 2026-08-23 08:55 UTCEG score recompute
  29. 2026-08-23 00:19 UTCEPSS rescore
  30. 2026-08-22 06:59 UTCEG score recompute
  31. 2026-08-21 23:49 UTCEPSS rescore
  32. 2026-08-21 05:04 UTCEG score recompute
  33. 2026-08-20 22:55 UTCEPSS rescore
  34. 2026-08-20 03:04 UTCEG score recompute
  35. 2026-08-19 17:03 UTCEPSS rescore
  36. 2026-08-19 00:54 UTCEG score recompute
  37. 2026-08-18 13:48 UTCEPSS rescore
  38. 2026-08-17 22:35 UTCEG score recompute
  39. 2026-08-17 13:47 UTCEPSS rescore
  40. 2026-08-16 19:39 UTCEG score recompute
  41. 2026-08-16 14:56 UTCEPSS rescore
  42. 2026-08-16 05:59 UTCEG score recompute
  43. 2026-08-16 02:14 UTCEPSS rescore
  44. 2026-08-15 04:05 UTCEG score recompute
  45. 2026-08-15 01:30 UTCEPSS rescore
  46. 2026-08-14 02:10 UTCEG score recompute
  47. 2026-08-13 22:00 UTCEPSS rescore
  48. 2026-08-13 00:16 UTCEG score recompute
  49. 2026-08-12 13:50 UTCEPSS rescore
  50. 2026-08-11 22:21 UTCEG score recompute
  51. 2026-08-11 13:42 UTCEPSS rescore
  52. 2026-08-11 09:22 UTCEG score recompute
  53. 2026-08-11 00:00 UTCEPSS rescore
  54. 2026-08-09 18:31 UTCEG score recompute
  55. 2026-08-09 13:46 UTCEPSS rescore
  56. 2026-08-08 16:37 UTCEG score recompute
  57. 2026-08-08 16:37 UTCEPSS rescore
  58. 2026-08-08 03:39 UTCEG score recompute
  59. 2026-08-07 01:45 UTCEG score recompute
  60. 2026-08-06 13:46 UTCEPSS rescore
  61. 2026-08-05 23:51 UTCEG score recompute
  62. 2026-08-05 19:17 UTCEPSS rescore
  63. 2026-08-04 21:54 UTCEG score recompute
  64. 2026-08-04 15:10 UTCEPSS rescore
  65. 2026-08-03 19:06 UTCEG score recompute
  66. 2026-08-03 10:36 UTCEPSS rescore
  67. 2026-08-02 03:47 UTCEG score recompute
  68. 2026-08-02 02:26 UTCEPSS rescore
  69. 2026-08-01 14:50 UTCEG score recompute
  70. 2026-08-01 04:16 UTCEPSS rescore
  71. 2026-07-30 23:17 UTCEG score recompute
  72. 2026-07-30 16:27 UTCEPSS rescore
  73. 2026-07-30 10:19 UTCEG score recompute
  74. 2026-07-30 01:30 UTCEPSS rescore
  75. 2026-07-28 17:50 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-26192?
CVE-2026-26192 is a high vulnerability published on July 7, 2026. Open WebUI vulnerable to Stored XSS via iFrame in citations model Summary Manually modifying chat history allows setting the html property within document metadata. This causes the frontend to enter a code path that treats document contents as HTML, and render them in an iFrame when the citation is…
When was CVE-2026-26192 disclosed?
CVE-2026-26192 was first published on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-26192 actively exploited?
CVE-2026-26192 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-26192?
CVE-2026-26192 has a CVSS base score of 7.3 (the CNA's own assessment, by github_m; NVD's own analysis pending).
How do I remediate CVE-2026-26192?
A fix for CVE-2026-26192 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-26192 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-26192

Explore →

Is Your Infrastructure Affected by CVE-2026-26192?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs