How severe is CVE-2025-22449?

CVE-2025-22449 has a CVSS score of 3.8/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-22449?

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

How do I fix CVE-2025-22449?

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

How do I detect CVE-2025-22449 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-22449 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-22449?

O3 pinpoints whether CVE-2025-22449 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-22449 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-22449 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-22449?

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

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

CVE-2025-22449 was published on January 9, 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-22449

LOW

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

Access control flaw for team admins allows unauthorized team additions

Also known asGHSA-q8fg-cp3q-5jwmGO-2025-3377

Published

Jan 9, 2025

Updated

Jul 15, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐹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 9.11.x <= 9.11.5 fail to enforce invite permissions, which allows team admins, with no permission to invite users to their team, to invite users by updating the "allow_open_invite" field via making their team public.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 9.11.0&&< 9.11.6	9.11.6
🐹Go	`github.com/mattermost/mattermost/server/v8`	all versions	8.0.0-20250102081831-64c566a8280b

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 9.11.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-22449 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-22449 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-22449. 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-22449 in your dependencies?

O3 detects CVE-2025-22449 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