CVE-2026-75587
CVE-2026-75587 — Plaintext pre-auth secret exposure via Desktop App diagnostics report
Mattermost Desktop App versions <=6.2 6.2.2.0 fail to redact the pre-auth secret when generating a diagnostics report, which allows a local attacker with access to a user's diagnostics report or log files to obtain the plaintext pre-auth secret configured for a connected server via inspecting the Server Connectivity (Step-3) diagnostics output. Mattermost Advisory ID: MMSA-2026-00716
Published Updated Sources: NVD, Mattermost (CNA), GitHub, GitHub Security Advisory, 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
0%
ahead of 0% of scored CVEs
CVSS base
3.6
low
Remediation
The vendor's own words where we have them.
Update Mattermost Desktop App to versions 6.3.0, 6.2.3.0 or higher.
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 |
|---|---|---|---|
| Mattermost | Mattermost | 0 to <= 6.2.2 | Vulnerable |
| Mattermost | Mattermost | 6.3.0 | Patched |
| Mattermost | Mattermost | 6.2.3.0 | Patched |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
None
Confidentiality
Low
Integrity
None
Scope
Changed
Attack Complexity
Low
Attack Vector
Local
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 |
|---|---|---|---|---|---|
| 3.6 | CVSS 3.1 | low | 1.8 | 1.4 | mattermost.com (CNA), Mattermost (CNA), GHSA |
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:L/I:N/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.
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- Read Application Data::
Mitigation: Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.::
Weakness & attack patterns
- CWE-200
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1562.003Impair Defenses: Impair Command History Logging
- T1574.006Hijack Execution Flow: Dynamic Linker Hijacking
- T1574.007Hijack Execution Flow: Path Interception by PATH Environment Variable
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
1
Social mentions
Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · GHSA-jq35-5w25-hqv7 published (low)
Aug 18, 2026 · GitHub Security Advisory
Added · CVSS 3.1 3.6 (AV:L)
Aug 17, 2026 · NVD
Initial · CVE published
Aug 17, 2026 · NVD
CVE published by mitre
Aug 17, 2026 · SOCRadar CTI
Source activity
Readings a source repeats on a schedule, counted rather than listed.
- 1×CVE modified by NIST, Modified, LinkAug 18, 2026 · SOCRadar CTI
References
3 on the record
- mattermost.com/security-updates
Vendor Advisory, NIST, Mitre
- nvd.nist.gov/vuln/detail/CVE-2026-75587
NVD
- github.com/advisories/GHSA-jq35-5w25-hqv7
Exploit, Third Party Advisory
Elsewhere on this site
- Mattermostevery CVE for this vendor
- Remote Code Execsame class
- CWE-200other 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-75587 is Plaintext pre-auth secret exposure via Desktop App diagnostics report, a low vulnerability affecting Mattermost from Mattermost. 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-75587. 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 3.6 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.
