CVE-2026-87997

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 4.3 from GitHub Security Advisory (severity: MODERATE) published 2026-09-10. A secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-75181 (ENISA EUVD) · GHSA-3pf7-q2g3-wj28 (GitHub Security Advisories) · PYSEC-2026-4118 (OSV.dev)Source: ENISA EUVD

4.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 4.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.10.0 until 0.11.1, POST /api/chat/completions and POST /api/v1/chat/completions in backend/open_webui/main.py copied a client-supplied folder_id into a new chat without applying the folder write-access check used by the dedicated chat routes. An authenticated user who knew a shared folder identifier could inject an attacker-controlled chat into a folder where the user had read-only or no write access, causing the entry to appear to authorized folder readers. This issue is fixed in version 0.11.1.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity43% × 45%
Impact severity (EG Severity): CVSS 4.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (4.3): severity, escalated by confirmed exploitation. This CVE's 4.3 is its impact severity (EG Severity), not escalated.

EG Severity
4.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 9, 2026

Last Modified

September 16, 2026

Advisory Details (4)

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

v0.11.1

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

https://github.com/open-webui/open-webui/releases/tag/v0.11.1
GitHub commit

commit d9e23b90c100 (open-webui/open-webui)

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

https://github.com/open-webui/open-webui/commit/d9e23b90c100d19b00270aea3cde0501d2354a6c
GitHub pull request

refac: share one folder write-access check across chat folder_id paths

Fix merged in open-webui/open-webui PR #28366 on 2026-08-11 — awaiting tagged release

https://github.com/open-webui/open-webui/pull/28366
GitHub advisoryMentions a patch (unverified)

Any authenticated user can inject chats into another user's folder via chat completions · Advisory · open-webui/open-webui · GitHub

Affected: 0.11.1 by

https://github.com/open-webui/open-webui/security/advisories/GHSA-3pf7-q2g3-wj28

Vendor Advisories for CVE-2026-87997(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipopen-webui @ 0.11.1 (fixes >= 0.10.0, < 0.11.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
open-webui0.10.0, 0.10.1, 0.10.2, 0.11.0
  • 0.10.0 up to 0.11.1: fixed in 0.11.1
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 90 is merged into the row it repeats.

  1. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-3pf7-q2g3-wj28 · GitHub severity MODERATE · GitHub CVSS 4.3
  4. 2026-11-01 07:37 UTCEG score recompute
  5. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-10-29 22:55 UTCOSV refresh
  8. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-25 13:53 UTCEG score recompute
  14. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-10-22 12:34 UTCEG score recompute
  18. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  19. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  20. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  21. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  22. 2026-10-18 03:03 UTCEG score recompute
  23. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  24. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  25. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
Show 64 more
  1. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  3. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  4. 2026-10-12 14:49 UTCEG score recompute
  5. 2026-10-11 19:15 UTCEG score recompute
  6. 2026-10-11 16:32 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-10-11 13:49 UTCEG score recompute
  9. 2026-10-11 07:17 UTCEG score recompute
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  11. 2026-10-10 01:07 UTCEG score recompute
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  13. 2026-10-08 23:56 UTCEG score recompute
  14. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  16. 2026-10-06 18:16 UTCEG score recompute
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  18. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-05 17:07 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-10-03 14:50 UTCEG score recompute
  22. 2026-10-02 13:20 UTCEG score recompute
  23. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  24. 2026-10-01 12:02 UTCEG score recompute
  25. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  26. 2026-09-30 10:42 UTCEG score recompute
  27. 2026-09-29 09:14 UTCEG score recompute
  28. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  29. 2026-09-28 07:54 UTCEG score recompute
  30. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  31. 2026-09-27 06:45 UTCEG score recompute
  32. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  33. 2026-09-26 05:35 UTCEG score recompute
  34. 2026-09-25 04:14 UTCEG score recompute
  35. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  36. 2026-09-24 03:05 UTCEG score recompute
  37. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  38. 2026-09-23 01:56 UTCEG score recompute
  39. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  40. 2026-09-22 00:48 UTCEG score recompute
  41. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  42. 2026-09-20 23:39 UTCEG score recompute
  43. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  44. 2026-09-19 22:31 UTCEG score recompute
  45. 2026-09-18 21:22 UTCEG score recompute
  46. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  47. 2026-09-17 20:14 UTCEG score recompute
  48. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  49. 2026-09-16 15:30 UTCEG score recompute
  50. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  51. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  52. 2026-09-15 15:39 UTCEG score recompute
  53. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  54. 2026-09-14 14:30 UTCEG score recompute
  55. 2026-09-14 13:50 UTCEG score recompute
  56. 2026-09-13 18:25 UTCEG score recompute
  57. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  58. 2026-09-12 17:16 UTCEG score recompute
  59. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  60. 2026-09-11 16:07 UTCEG score recompute
  61. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  62. 2026-09-09 22:31 UTCEG score recompute
  63. 2026-09-09 21:41 UTCEG score recomputeFirst assessed: 4.3 MEDIUM
  64. 2026-09-09 21:40 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-87997?
CVE-2026-87997 is a medium-severity vulnerability; its CVE record was published on September 9, 2026. Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.10.0 until 0.11.1, POST /api/chat/completions and POST /api/v1/chat/completions in backend/open_webui/main.py copied a client-supplied folder_id into a new chat without applying the folder write-access…
When was the CVE record for CVE-2026-87997 published?
The CVE record for CVE-2026-87997 was published on September 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 16, 2026; the record at its source may have been updated since.
Is CVE-2026-87997 actively exploited?
CVE-2026-87997 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-87997?
CVE-2026-87997 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-87997?
A fix for CVE-2026-87997 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-87997 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-87997

Explore →

Is Your Infrastructure Affected by CVE-2026-87997?

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