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.2%, top 91% 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%CVSS: 7.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.3(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
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 rangeFixed inDependents
open-webui0.1.124 ... 0.6.9 (135 versions)0.7.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 53× 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.

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

Related CVEs(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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 90.9% of all scored CVEs.
What is the CVSS score of CVE-2026-26192?
CVE-2026-26192 has a CVSS v4.0 base score of 7.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-26192?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-26192, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs