How severe is CVE-2025-64641?

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

Which packages are affected by CVE-2025-64641?

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

How do I fix CVE-2025-64641?

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

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

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

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

CVE-2025-64641 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-64641 published, and has it been updated?

CVE-2025-64641 was published on December 24, 2025 and was last updated on July 31, 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-64641

MEDIUM

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

Mattermost Jira plugin crafted action leaks Jira issue details

Also known asGHSA-vww6-79rv-3j4xGO-2025-4260

Published

Dec 24, 2025

Updated

Jul 31, 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🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server

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 11.1.x <= 11.1.0, 11.0.x <= 11.0.5, 10.12.x <= 10.12.3, 10.11.x <= 10.11.7 fail to verify that post actions invoking /share-issue-publicly were created by the Jira plugin which allowed a malicious Mattermost user to exfiltrate Jira tickets when victim users interacted with affected posts

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost/server/v8`	all versions	8.0.0-20251121122154-b57c297c6d7
🐹Go	`github.com/mattermost/mattermost-server`	≥ 10.11.0&&< 10.11.8	10.11.8
🐹Go	`github.com/mattermost/mattermost-server`	≥ 10.12.0&&< 10.12.4	10.12.4
🐹Go	`github.com/mattermost/mattermost-server`	≥ 11.0.0&&< 11.0.6	11.0.6
🐹Go	`github.com/mattermost/mattermost-server`	≥ 11.1.0&&< 11.1.1	11.1.1

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

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