CVE-2026-9571

MEDIUMNVD 6.55.9
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory published 2026-07-13. NVD baseline CVSS 6.5; sources differ by 0.6.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Mattermost versions 11.7.x <= 11.7.2, 11.6.x <= 11.6.4, 10.11.x <= 10.11.19 fail to invalidate OAuth refresh tokens upon user account deactivation, which allows a deactivated user or an attacker in possession of a valid refresh token to obtain new functional access tokens via the OAuth refresh token grant endpoint.. Mattermost Advisory ID: MMSA-2026-00680

CVSS v3
6.5
EG Score
5.9(high)
EPSS
7.0%
KEV
Not listed

Published

July 13, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated Jul 13, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-9571(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 0× in last 7d / 0× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 09:31 UTCEG score recompute
  3. 2026-07-15 09:30 UTCGHSA enrichment
  4. 2026-07-15 06:20 UTCNVD updateCVSS v3 → 6.5
  5. 2026-07-15 04:19 UTCMITRE cvelistV5CVSS v3 → 5.9
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-14 15:20 UTCNVD updateCVSS v3 → 6.5
  8. 2026-07-14 15:05 UTCMITRE cvelistV5CVSS v3 → 5.9
  9. 2026-07-14 09:08 UTCEG score recompute
  10. 2026-07-14 09:08 UTCGHSA enrichment
  11. 2026-07-13 22:31 UTCEPSS rescore
  12. 2026-07-13 22:08 UTCNVD updateCVSS v3 → 6.5
  13. 2026-07-13 08:43 UTCEG score recompute
  14. 2026-07-13 08:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-9571?
CVE-2026-9571 is a medium vulnerability published on July 13, 2026. Mattermost versions 11.7.x <= 11.7.2, 11.6.x <= 11.6.4, 10.11.x <= 10.11.19 fail to invalidate OAuth refresh tokens upon user account deactivation, which allows a deactivated user or an attacker in possession of a valid refresh token to obtain new functional access tokens via the OAuth refresh…
When was CVE-2026-9571 disclosed?
CVE-2026-9571 was first published in the National Vulnerability Database on July 13, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9571 actively exploited?
CVE-2026-9571 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9571?
CVE-2026-9571 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 5.9.
How do I remediate CVE-2026-9571?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9571, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-9571

Explore →

Is Your Infrastructure Affected by CVE-2026-9571?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.