CVE-2026-87016

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

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

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

Also known asEUVD-2026-75176 (ENISA EUVD) · GHSA-wpmr-8h3q-fwj7 (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.6%CVSS: 8.1Exploit: 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.6.41 until 0.11.1, get_user_by_oauth_sub and get_user_by_scim_external_id in backend/open_webui/models/users.py used JSON contains matching that compiled to SQL LIKE substring matching on SQLite. An OAuth subject containing percent or underscore wildcard characters could resolve to a different stored identity, potentially selecting an administrator account and issuing the attacker that account's session; PostgreSQL deployments were not affected. This issue is fixed in version 0.11.1.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
48th
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 (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 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, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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 15, 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 73c1f5806aeb (open-webui/open-webui)

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

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

refactor: match provider identity lookups via JSON subscript

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

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

Sign-in as another user via wildcard characters in the OAuth subject claim on SQLite · Advisory · open-webui/open-webui · GitHub

Affected: 0.11.1 by

https://github.com/open-webui/open-webui/security/advisories/GHSA-wpmr-8h3q-fwj7

Vendor Advisories for CVE-2026-87016(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.6.41, < 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.9.6 (30 versions)
  • 0.6.41 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 / 48× 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. 2 repeat rows among the latest 93 are merged into the row they repeat.

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

Frequently asked(5)

What is CVE-2026-87016?
CVE-2026-87016 is a high-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.6.41 until 0.11.1, get_user_by_oauth_sub and get_user_by_scim_external_id in backend/open_webui/models/users.py used JSON contains matching that compiled to SQL LIKE substring matching on SQLite. An OAuth…
When was the CVE record for CVE-2026-87016 published?
The CVE record for CVE-2026-87016 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 15, 2026; the record at its source may have been updated since.
Is CVE-2026-87016 actively exploited?
CVE-2026-87016 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-87016?
CVE-2026-87016 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-87016?
A fix for CVE-2026-87016 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-87016 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-87016

Explore →

Is Your Infrastructure Affected by CVE-2026-87016?

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