CVE-2026-18075: Revoked OAuth app retains access to real-time events via already-open WebSocket connection
Mattermost versions 11.11.x <= 11.11.0, 11.7.x <= 11.7.11, 11.10.x <= 11.10.2 fail to invalidate cached WebSocket session state when an OAuth app is deleted, which allows a revoked OAuth integration to keep receiving real-time events, including private channel posts, via a WebSocket connection that was already open when the app was deleted.. Mattermost Advisory ID: MMSA-2026-00745
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 12.0.0
Event History
Frequently Asked Questions
What conditions are required for exploitation?
An OAuth integration must already have an authenticated WebSocket connection open when the app is deleted. The issue affects cached session state on that existing connection; the description does not indicate that a new connection can be established after revocation.
Who could be exposed to the retained event stream?
A revoked OAuth integration that maintained an open WebSocket connection can continue receiving real-time events, including private channel posts. Exposure is limited to events available through that connection's prior OAuth session.
How can administrators tell whether they may be affected?
Review whether OAuth apps were deleted while they had active WebSocket connections, particularly on affected Mattermost releases. A revoked app that remains connected and continues receiving real-time events after deletion indicates the issue.
What can be done if updating is not immediately possible?
The described condition depends on a WebSocket connection already being open at the time of deletion. Administrators should ensure revoked OAuth integrations do not retain existing WebSocket connections when removing them.