Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privilege user
-
ExploitQuery user status API for target
-
ExecutionRead unsanitized active channel field
-
ImpactInfer private channel ID membership activity
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Outbound data filtering
|
| Exploitation Conditions | Requires a valid authenticated account on the target Mattermost server (PR:L) with network access to the user status API endpoints; no membership in the target private channel is needed, which is precisely the flaw. Limiting factors: the attacker must already be a provisioned user on the same instance, exploitation only reveals the channel ID of a private channel another user is actively viewing (not its contents, name, or member list), and the leak depends on the victim actively viewing the channel at query time. Affected only on Mattermost 11.9.x ≤ 11.9.1, 11.8.x ≤ 11.8.5, 11.7.x ≤ 11.7.10, and 11.10.x ≤ 11.10.1; instances on fixed builds or other release lines are not affected. |
| Impact | This is a low-to-moderate severity information disclosure flaw (CVSS 4.3) that is a genuine but low-urgency issue rather than an emergency. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) indicates network-reachable, low-complexity exploitation but requires low-privilege authentication (PR:L) and yields only limited confidentiality impact (C:L) with no integrity or availability impact. Per CWE-201, the leak is narrow: an authenticated user can learn the channel ID of a private channel another user is actively viewing via the status API, without membership. EPSS score was not provided in the input and cannot be assessed. There is no public exploit identified at time of analysis, and the CVE is not listed in CISA KEV, so there is no evidence of active exploitation. All signals are internally consistent - low real-world risk: exploitation requires an existing authenticated account on the Mattermost instance and leaks only a channel identifier (not channel contents, names, or membership), making this primarily a privacy/metadata-leak concern useful for internal reconnaissance rather than a direct compromise vector. |
| Exploit ScenarioDerived | An authenticated low-privilege Mattermost user repeatedly polls the user status API endpoints to read the unsanitized active channel field for a targeted user. By observing the returned private channel IDs over time, the attacker maps which private channels a victim is actively viewing despite having no membership in them. No public proof-of-concept exists, and exploitation is low-complexity (AC:L) once the attacker holds any valid account. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
Information disclosure in Mattermost release lines 11.7.x, 11.8.x, 11.9.x and 11.10.x (up to 11.7.10, 11.8.5, 11.9.1 and 11.10.1 respectively) allows an authenticated user to learn the channel ID of a private channel that another user is actively viewing. The user status API endpoints return an unsanitized active-channel field, so any provisioned account on the same server - with no membership in the target private channel, which is precisely the flaw - can query another user's status and observe which private channel that user is currently reading. The exposure is limited to the channel identifier itself, not its contents, name or membership, but it still reveals the existence of private channels and correlates named users with sensitive collaboration spaces. Rated CVSS 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N), this is a low-to-moderate urgency issue rather than an emergency, and no public exploit has been identified at time of analysis.
RemediationAI
This issue is fixed in later builds of each affected release line; no exact fixed version number is supplied in the available data, so consult the Mattermost security updates page at https://mattermost.com/security-updates and the MMSA-2026-00765 entry to identify and deploy the patched build corresponding to your branch, then confirm no instance remains on 11.7.10, 11.8.5, 11.9.1 or 11.10.1 or earlier. If immediate upgrading is not possible, the most direct compensating control is to reduce the population of authenticated accounts that can read the status endpoints - tighten team and server invitation policies, audit and deactivate stale accounts, and disable open self-registration - since the flaw requires only a valid provisioned account and no channel membership; the trade-off is administrative overhead and a smaller legitimate user base. Where a reverse proxy or API gateway fronts the server, throttling or blocking bulk polling of the user status endpoints (/api/v4/users/status/ids and related status routes) for untrusted clients limits enumeration throughput, but Mattermost's own web and desktop clients rely on these endpoints for presence, so aggressive blocking will visibly break presence indicators and sidebar updates. Finally, treat the leaked channel identifiers as sensitive: review private channel membership and naming hygiene, and be aware that this attack is a quiet read with no reliable server-side signal that a specific lookup was malicious, so monitoring is a detective rather than preventive measure.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is an instance of CWE-201 (Insertion of Sensitive Information Into Sent Data) in Mattermost's user status subsystem. Mattermost clients surface presence information - online/away status, and the channel a user is currently focused on - through its status API endpoints, which client UIs poll so that sidebar and presence indicators stay current. Those endpoints are readable by any authenticated user on the instance by design, since presence is generally considered non-sensitive. In the affected builds, the 'active channel' value embedded in that status payload is returned without sanitization or authorization filtering, meaning the server does not suppress or mask the channel identifier when the referenced channel is private and the requesting user is not a member. The result is a broken access control of the indirect-object-reference variety layered on top of an information-leakage weakness: the API transmits data the caller should not be entitled to see. Mattermost's own advisory for this issue is MMSA-2026-00765, tracked publicly as CVE-2026-19603; no CPE strings were supplied in the source data, so the authoritative product scope is the vendor's advisory rather than a CPE enumeration. Nothing in the available data suggests memory corruption, injection, or a path to code execution - this is purely a read-side disclosure whose severity is bounded by the low confidentiality-only impact assigned in the CVSS vector.
Know when Mattermost gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Network API reachable with low complexity, but requires a provisioned authenticated account (PR:L); only a channel ID leaks, so C:L with no integrity or availability impact.
Primary rating from Vendor (mattermost).
CVSS VectorVendor: mattermost
DescriptionCVE.org
Mattermost versions 11.9.x <= 11.9.1, 11.8.x <= 11.8.5, 11.7.x <= 11.7.10, 11.10.x <= 11.10.1 fail to sanitize the active channel field returned by the user status API endpoints, which allows an authenticated user to learn the channel ID of a private channel another user is actively viewing via the status endpoints, without being a member of that channel. Mattermost Advisory ID: MMSA-2026-00765
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Mattermost
View allMattermost versions 10.4.x <= 10.4.1, 9.11.x <= 9.11.7, 10.3.x <= 10.3.2, 10.2.x <= 10.2.2 fail to properly validate boa
Denial of service in linkify-it (npm) through v5.0.0 lets remote unauthenticated attackers wedge a rendering worker by s
A denial-of-service vulnerability in Mattermost allows an authenticated user to crash the server via multiple large auto
Mattermost version 7.1.x and earlier fails to sufficiently process a specifically crafted GIF file when it is uploaded w
A remote code execution vulnerability (CVSS 9.9) that allows authenticated users. Critical severity with potential for s
Mattermost versions 10.4.x <= 10.4.1, 9.11.x <= 9.11.7, 10.3.x <= 10.3.2, 10.2.x <= 10.2.2 fail to properly validate inp
Privilege escalation to full administrative control in Mattermost self-hosted server (versions 11.6.0 and earlier in the
Mattermost versions 11.0.x <= 11.0.2, 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12 fail to to verify that t
Mattermost versions 10.12.x <= 10.12.1, 10.11.x <= 10.11.4, 10.5.x <= 10.5.12, 11.0.x <= 11.0.3 fail to properly validat
Mattermost webapp fails to validate route parameters in/<TEAM_NAME>/channels/<CHANNEL_NAME> allowing an attacker to perf
Fleet is an open source osquery manager. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable,
Mattermost versions 10.4.x <= 10.4.1, 9.11.x <= 9.11.7, 10.3.x <= 10.3.2, 10.2.x <= 10.2.2 fail to use prepared statemen
EUVD-2026-102742
GHSA-7ggq-hqj4-w5vc
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB