CVE-2026-59217

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 81% 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: epss, secondary
Trending — 3 sources updated this weekElevated
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

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

Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. Prior to 0.10.0, the file upload path accepted metadata.knowledge_id and auto-linked uploaded files to a target knowledge base without applying the write-access check used by /api/v1/knowledge//file/add, allowing read-only knowledge-base users to add arbitrary files. This issue is fixed in version 0.10.0.

CVSS v3
4.3
EG Score
4.3(medium)
EPSS
19.1%
KEV
Not listed

Published

July 9, 2026

Last Modified

July 14, 2026

Advisory Details (4)

Auto-updated Jul 9, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

Upload `metadata.knowledge_id` bypasses the knowledge-base write-access check (read-only users can add files to KB) · Advisory · open-webui/open-webui · GitHub

https://github.com/open-webui/open-webui/security/advisories/GHSA-7r7x-gjvr-448g
github_release Patch Available

v0.10.0

Patch available: open-webui/open-webui v0.10.0

https://github.com/open-webui/open-webui/releases/tag/v0.10.0
github_pr

Authorize KB write access before auto-linking an uploaded file

Fix merged in open-webui/open-webui PR #26001 on 2026-06-16 — awaiting tagged release

https://github.com/open-webui/open-webui/pull/26001
github_commit

commit b7626f05fb92 (open-webui/open-webui)

Fix landed in open-webui/open-webui commit b7626f05fb92 — awaiting tagged release

https://github.com/open-webui/open-webui/commit/b7626f05fb92b24ab923ad81a037071ebd5623d1

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 15× 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-07-15 02:00 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-14 13:47 UTCEG score recompute
  4. 2026-07-13 22:31 UTCEPSS rescore
  5. 2026-07-13 14:28 UTCEG score recompute
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-13 06:13 UTCEPSS rescore
  8. 2026-07-12 15:10 UTCEG score recompute
  9. 2026-07-12 05:46 UTCEPSS rescore
  10. 2026-07-11 15:52 UTCEG score recompute
  11. 2026-07-11 08:27 UTCEPSS rescore
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-10 16:35 UTCEG score recompute
  14. 2026-07-09 17:18 UTCEG score recompute
  15. 2026-07-09 17:15 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-59217?
CVE-2026-59217 is a medium vulnerability published on July 9, 2026. Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. Prior to 0.10.0, the file upload path accepted metadata.knowledge_id and auto-linked uploaded files to a target knowledge base without applying the write-access check used by /api/v1/knowledge//file/add, allowing…
When was CVE-2026-59217 disclosed?
CVE-2026-59217 was first published in the National Vulnerability Database on July 9, 2026, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59217 actively exploited?
CVE-2026-59217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-59217?
CVE-2026-59217 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-59217?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59217, 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

Explore the affected products and dependency analysis for CVE-2026-59217

Explore →

Is Your Infrastructure Affected by CVE-2026-59217?

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

Start Free Scan →Browse All CVEs