Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

GHSA-vww6-79rv-3j4x v8

MEDIUMFix: mattermost/mattermost#34551

GHSA-vww6-79rv-3j4x is a medium-severity (CVSS 4.1) CWE-863 vulnerability in github.com/mattermost/mattermost/server/v8. A fix is available for github.com/mattermost/mattermost/server/v8 — see the affected versions and patch details below.

Mattermost doesn't verify that post actions invoking `/share-issue-publicly` were created by the Jira plugin

Also known asCVE-2025-64641GO-2025-4260
Published
Dec 24, 2025
Updated
Feb 27, 2026
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-vww6-79rv-3j4x.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs7th percentile — riskier than 7% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-vww6-79rv-3j4x plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

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
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/mattermost/mattermost/server/v8all versions8.0.0-20251121122154-b57c297c6d7go get github.com/mattermost/mattermost/server/v8@v8.0.0-20251121122154-b57c297c6d7
🐹Gogithub.com/mattermost/mattermost-server10.11.0&&< 10.11.810.11.8go get github.com/mattermost/mattermost-server@v10.11.8
🐹Gogithub.com/mattermost/mattermost-server10.12.0&&< 10.12.410.12.4go get github.com/mattermost/mattermost-server@v10.12.4
🐹Gogithub.com/mattermost/mattermost-server11.0.0&&< 11.0.611.0.6go get github.com/mattermost/mattermost-server@v11.0.6
🐹Gogithub.com/mattermost/mattermost-server11.1.0&&< 11.1.111.1.1go get github.com/mattermost/mattermost-server@v11.1.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost/server/v8, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. 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 GHSA-vww6-79rv-3j4x is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-vww6-79rv-3j4x can be triaged on real exposure rather than presence alone.

Tailored to GHSA-vww6-79rv-3j4x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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
O3 Security · Impact-Aware SCA

Is GHSA-vww6-79rv-3j4x in your dependencies?

O3 Security finds GHSA-vww6-79rv-3j4x across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-vww6-79rv-3j4x: v8 (Medium 4.1) | O3 Security