Skip to content

GHSA-vqp5-2mrp-qqxg CVE-2026-6333 GO-2026-5671

Mattermost doesn't validate the Host header when constructing response URLs for custom slash command

Medium Go
Severity
3.5 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.14%
Chance of exploitation in the next 30 days. Higher than 3.08% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-918 Server-Side Request Forgery (SSRF)
Fix
Available
2 packages have a fixed version

Description

Mattermost versions 11.5.x <= 11.5.1, 10.11.x <= 10.11.13 fail to validate the Host header when constructing response URLs for custom slash commands which allows an authenticated attacker to redirect slash command responses to an attacker-controlled server via a spoofed Host header.. Mattermost Advisory ID: MMSA-2026-00582

Affected versions

Go

PackageVulnerableFixed in
github.com/mattermost/mattermost-server
< 5.3.2-0.20260325160634-e738016c5920
5.3.2-0.20260325160634-e738016c5920
github.com/mattermost/mattermost-server
>= 10.11.0+incompatible, < 10.11.14+incompatible
>= 11.5.0+incompatible, < 11.5.2+incompatible
10.11.14+incompatible
11.5.2+incompatible
github.com/mattermost/mattermost-server/v5
all versions
No fix yet
github.com/mattermost/mattermost-server/v6
all versions
No fix yet
github.com/mattermost/mattermost/server/v8
>= 11.5.0, < 11.5.2
11.5.2
github.com/mattermost/mattermost/server/v8
>= 10.11.0, < 10.11.14
10.11.14
github.com/mattermost/mattermost/server/v8
< 8.0.0-20260325160634-e738016c5920
8.0.0-20260325160634-e738016c5920

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/mattermost/mattermost-server Go → 5.3.2-0.20260325160634-e738016c5920

go
go get github.com/mattermost/mattermost-server@v5.3.2-0.20260325160634-e738016c5920 && go mod tidy

github.com/mattermost/mattermost/server/v8 Go → 11.5.2

go
go get github.com/mattermost/mattermost/server/v8@v11.5.2 && go mod tidy

Severity breakdown

CVSS 3.1 3.5

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
None

Weakness

CWE-918: Server-Side Request Forgery (SSRF)

The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-xmfh-3ccg-c9fx
Mattermost has an Incorrect Authorization issue
Low Also affects github.com/mattermost/mattermost-server
GHSA-h998-hxxj-8q83
Mattermost doesn't invalidate cached authentication state for active WebSocket connections during global session revocation
Medium Also affects github.com/mattermost/mattermost-server
GHSA-g5vr-6pgg-74qv
Mattermost doesn't enforce bot-specific permission checks on the user active status endpoint
Low Also affects github.com/mattermost/mattermost-server
GHSA-jqgv-39mg-7c2r
Mattermost doesn't authenticate Atlassian Connect installed callbacks, allowing a remote unauthenticated attacker to inject a rogue sharedSecret
Medium Also affects github.com/mattermost/mattermost-server
GHSA-mxq2-5jpg-7474
Mattermost doesn't validate channel ownership of an existing subscription before applying edits
Medium Also affects github.com/mattermost/mattermost-server
GHSA-2g8v-grq3-hq2g
Mattermost doesn't enforce administrator authorization on the {{setDefaultInstance}} call within the {{/gitlab connect}} command handler
Medium Also affects github.com/mattermost/mattermost-server
GHSA-6hxm-w4hv-vgvw
Mattermost doesn't require role-management authorization when setting the scheme_admin flag on group syncable link and patch endpoints
High Also affects github.com/mattermost/mattermost-server
GHSA-9p44-r552-4wp9
Mattermost doesn't sanitize the Remote Cluster API response on PATCH operations
Medium Also affects github.com/mattermost/mattermost-server
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor