How severe is GHSA-hm95-jx66-g2gh?

GHSA-hm95-jx66-g2gh has a CVSS score of 3.1/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-hm95-jx66-g2gh?

GHSA-hm95-jx66-g2gh affects the following packages: github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost-server (Go). Ecosystems affected: Go.

How do I fix GHSA-hm95-jx66-g2gh?

Update github.com/mattermost/mattermost/server/v8 to 8.0.0-202508080704-39bd251fe4f600 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hm95-jx66-g2gh is resolved across your whole dependency graph.

How do I detect GHSA-hm95-jx66-g2gh 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 GHSA-hm95-jx66-g2gh 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 GHSA-hm95-jx66-g2gh?

O3 pinpoints whether GHSA-hm95-jx66-g2gh 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 GHSA-hm95-jx66-g2gh actively exploited in the wild?

No public exploit code has been indexed for GHSA-hm95-jx66-g2gh 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 GHSA-hm95-jx66-g2gh?

GHSA-hm95-jx66-g2gh is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hm95-jx66-g2gh published, and has it been updated?

GHSA-hm95-jx66-g2gh was published on September 15, 2025 and was last updated on September 17, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-hm95-jx66-g2gh

LOWFix: mattermost/mattermost@39bd251

GHSA-hm95-jx66-g2gh is a low-severity (CVSS 3.1) Open Redirect vulnerability in github.com/mattermost/mattermost/server/v8. O3 Security confirms whether GHSA-hm95-jx66-g2gh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Mattermost Open Redirect vulnerability

Also known asCVE-2025-9084GO-2025-3960

Published

Sep 15, 2025

Updated

Sep 17, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Real-World Exposure

2 pkgs affected

🐹github.com/mattermost/mattermost/server/v8🐹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 10.5.x <= 10.5.9 fail to properly validate redirect URLs which allows attackers to redirect users to malicious sites via crafted OAuth login URLs.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost/server/v8`	all versions	8.0.0-202508080704-39bd251fe4f600
🐹Go	`github.com/mattermost/mattermost-server`	≥ 10.5.0&&< 10.5.10	10.5.10

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-202508080704-39bd251fe4f600 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hm95-jx66-g2gh 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 GHSA-hm95-jx66-g2gh 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 GHSA-hm95-jx66-g2gh. 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 10.5.x <= 10.5.9 fail to properly validate redirect URLs which allows attackers to redirect users to malicious sites via crafted OAuth login URLs.

O3 Security · Impact-Aware SCA

Is GHSA-hm95-jx66-g2gh in your dependencies?

O3 detects GHSA-hm95-jx66-g2gh 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