What is CVE-2026-87015?

CVE-2026-87015 is Open WebUI: A user's session cookies are sent to tool servers configured for bearer authentication. The supplied enrichment data classifies it as Unclassified mapped to CWE-201 CWE-201.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-87015. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-87015 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

1 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-87015 using CVSS 6.8, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

mediumpublic exploit

CVE-2026-87015

CVE-2026-87015 — Open WebUI: A user's session cookies are sent to tool servers configured for bearer authentication

Open WebUI is an extensible, feature-rich, and user-friendly self-hosted AI platform. From 0.6.27 until 0.11.1, backend/open_webui/utils/tools.py captured a cookie jar from the enclosing connection loop instead of binding it to each external tool callable. When multiple tool servers were attached and a session or system OAuth connection was processed last, a request to a different server configured for bearer authentication could include the calling user's Open WebUI session cookies, allowing that server's operator to reuse the session and take over the account. This issue is fixed in version 0.11.1.

Published Sep 9, 2026Updated Sep 9, 2026Sources: NVD, open-webui (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

open-webui

CVSS base

6.8

medium

Remediation

The vendor's own words where we have them.

Upgrade open-webui to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
open-webui	open-webui	>= 0.6.27, < 0.11.1	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

None

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

High

Attack Vector

Network

Privileges Req

None

User Interaction

Required

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
6.8	CVSS 3.1	medium	1.6	5.2	GitHub (CNA), open-webui (CNA)

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-201 · Insertion of Sensitive Information Into Sent Data

Read Files or Directories
Read Memory
Read Application Data

Mitigation: Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.

Weakness & attack patterns

CWE-201

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-12 · Choosing Message IdentifierCAPEC-217 · Exploiting Incorrectly Configured SSLCAPEC-613 · WiFi SSID TrackingCAPEC-612 · WiFi MAC Address TrackingCAPEC-618 · Cellular Broadcast Message RequestCAPEC-619 · Signal Strength TrackingCAPEC-621 · Analysis of Packet Timing and SizesCAPEC-622 · Electromagnetic Side-Channel AttackCAPEC-623 · Compromising Emanations Attack

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Search application, proxy, and WAF logs for requests touching /open_webui/utils/tools.py.
Prioritize edge telemetry for network-reachable open-webui.
Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 6.8 (AV:N)
Sep 9, 2026 · NVD
Initial · CVE published
Sep 9, 2026 · NVD
CVE published by MITRE.
Sep 9, 2026 · SOCRadar CTI

References

4 on the record

github.com/open-webui/open-webui/commit/cd9db21c5276807a2975ddba17cef369ad1114b7
Exploit, Third Party Advisory, Mitre
github.com/open-webui/open-webui/pull/28630
Exploit, Third Party Advisory, Mitre
github.com/open-webui/open-webui/releases/tag/v0.11.1
Exploit, Third Party Advisory, Mitre
github.com/open-webui/open-webui/security/advisories/GHSA-p78m-89r6-pgf7
Exploit, Third Party Advisory, Mitre

Elsewhere on this site

open-webuievery CVE for this vendor
Unclassifiedsame class
CWE-201other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-87015 is Open WebUI: A user's session cookies are sent to tool servers configured for bearer authentication, a medium vulnerability affecting open-webui from open-webui. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-87015. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 6.8 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.