How severe is CVE-2025-2571?

CVE-2025-2571 has a CVSS score of 4.2/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-2571?

CVE-2025-2571 affects the following packages: github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go). Ecosystems affected: Go.

How do I fix CVE-2025-2571?

Update github.com/mattermost/mattermost/server/v8 to 10.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-2571 is resolved across your whole dependency graph.

How do I detect CVE-2025-2571 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost/server/v8. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2025-2571 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-2571?

O3 pinpoints whether CVE-2025-2571 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2025-2571 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-2571 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is CVE-2025-2571?

CVE-2025-2571 is classified as CWE-303 (CWE-303). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-2571 published, and has it been updated?

CVE-2025-2571 was published on May 30, 2025 and was last updated on July 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

CVE-2025-2571

MEDIUM

CVE-2025-2571 is a medium-severity (CVSS 4.2) CWE-303 vulnerability in github.com/mattermost/mattermost/server/v8. O3 Security confirms whether CVE-2025-2571 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Google OAuth Authentication Bypass for Converted Bot Accounts

Also known asGHSA-8cgx-9ccj-3gwrGO-2025-3729

Published

May 30, 2025

Updated

Jul 15, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Blast Radius

5 pkgs affected

🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Mattermost versions 10.7.x <= 10.7.0, 10.6.x <= 10.6.2, 10.5.x <= 10.5.3, 9.11.x <= 9.11.12 fail to clear Google OAuth credentials when converting user accounts to bot accounts, allowing attackers to gain unauthorized access to bot accounts via the Google OAuth signup flow.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 10.7.0-rc1&&< 10.7.1	10.7.1
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 10.0.0-rc1&&< 10.5.4	10.5.4
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 9.0.0-rc1&&< 9.11.13	9.11.13
🐹Go	`github.com/mattermost/mattermost/server/v8`	all versions	8.0.0-20250414095146-04676582cdd2
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 10.6.0-rc1&&< 10.6.3	10.6.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost/server/v8. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/mattermost/mattermost/server/v8 to 10.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-2571 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-2571 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-2571. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2025-2571 in your dependencies?

O3 detects CVE-2025-2571 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works