CVE-2026-12985
CVE-2026-12985 — Mattermost DCR redirect URI allowlist bypass via improper URL component validation
Mattermost versions 11.9.x <= 11.9.0, 11.8.x <= 11.8.4, 11.7.x <= 11.7.7 Mattermost failed to validate Dynamic Client Registration redirect URIs by URL component (matching glob patterns against the raw URI string instead) which allows a remote unauthenticated attacker to register an OAuth client with an attacker-controlled callback host that bypasses the configured redirect URI allowlist via a crafted redirect URI that places an allowlisted host/path suffix inside the query string.. Mattermost Advisory ID: MMSA-2026-00700
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
6.8
medium
Remediation
The vendor's own words where we have them.
Update Mattermost to versions 11.10.0, 11.9.1, 11.8.5, 11.7.8 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 | 11.9.0 to <= 11.9.0 | Vulnerable |
| Mattermost | Mattermost | 11.8.0 to <= 11.8.4 | Vulnerable |
| Mattermost | Mattermost | 11.7.0 to <= 11.7.7 | Vulnerable |
| Mattermost | Mattermost | 11.10.0 | Patched |
| Mattermost | Mattermost | 11.9.1 | Patched |
| Mattermost | Mattermost | 11.8.5 | Patched |
| Mattermost | Mattermost | 11.7.8 | Patched |
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 | mattermost.com (CNA), Mattermost (CNA), GHSA |
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.
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
- Bypass Protection Mechanism
- Gain Privileges or Assume Identity
- Other
Mitigation: Assume all input is malicious. Use an accept known good input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, boat may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as red or blue. Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright. Use a list of approved URLs or domains to be used for redirection.
Weakness & attack patterns
- CWE-601
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
3
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 /path.
- Prioritize edge telemetry for network-reachable Mattermost.
- Monitor for scanner or exploit-pattern traffic after 3 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 · CVSS 3.1 6.8 (AV:N)
Sep 14, 2026 · NVD
Initial · CVE published
Sep 14, 2026 · NVD
Added · GHSA-c92j-r2f4-67xg published (medium)
Sep 14, 2026 · GitHub Security Advisory
CVE published by MITRE.
Sep 14, 2026 · SOCRadar CTI
References
3 on the record
- mattermost.com/security-updates
Vendor Advisory, Mitre
- nvd.nist.gov/vuln/detail/CVE-2026-12985
NVD
- github.com/advisories/GHSA-c92j-r2f4-67xg
Exploit, Third Party Advisory
Elsewhere on this site
- Mattermostevery CVE for this vendor
- Unclassifiedsame class
- CWE-601other 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-12985 is Mattermost DCR redirect URI allowlist bypass via improper URL component validation, a medium 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-12985. Public exploit evidence is: 3 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.