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

Mattermost doesn't validate the Host header when constructing response URLs for custom slash command in github.com/mattermost/mattermost-server

Published 25 Jun 2026 · Updated 25 Jun 2026

Is your project on an affected github.com/mattermost/mattermost-server?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=10.11.0+incompatible <10.11.14+incompatible · >=11.5.0+incompatible <11.5.2+incompatible
Fixed in
10.11.14+incompatible, 11.5.2+incompatible
Update to the fixed version for your release line, for example:go get github.com/mattermost/mattermost-server@v11.5.2+incompatible
Affected
All versions
Fixed in
No fix released
Affected
All versions
Fixed in
No fix released
Affected
<8.0.0-20260325160634-e738016c5920
Fixed in
8.0.0-20260325160634-e738016c5920
Update to the fixed version for your release line, for example:go get github.com/mattermost/mattermost/server/v8@v8.0.0-20260325160634-e738016c5920

Details

Mattermost doesn't validate the Host header when constructing response URLs for custom slash command in github.com/mattermost/mattermost-server.

NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.

(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)

The additional affected modules and versions are: github.com/mattermost/mattermost-server/v5 before v5.3.2-0.20260325160634-e738016c5920.

Is GO-2026-5671 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/mattermost/mattermost-server, and gives you the command that fixes it.

More advisories for github.com/mattermost/mattermost-server

  • LowCVE-2026-8823Mattermost has an Incorrect Authorization issue in github.com/mattermost/mattermost-server · 1 Oct 2026
  • LowCVE-2026-5139Mattermost doesn't enforce administrator authorization on the {{setDefaultInstance}} call within the {{/gitlab connect}} command handler in github.com/mattermost/mattermost-server · 28 Sept 2026
  • LowCVE-2026-8074Mattermost doesn't enforce bot-specific permission checks on the user active status endpoint in github.com/mattermost/mattermost-server · 28 Sept 2026
  • LowCVE-2026-9162Mattermost doesn't invalidate cached authentication state for active WebSocket connections during global session revocation in github.com/mattermost/mattermost-server · 28 Sept 2026
  • LowCVE-2026-6673Mattermost doesn't authenticate Atlassian Connect installed callbacks, allowing a remote unauthenticated attacker to inject a rogue sharedSecret in github.com/mattermost/mattermost-server · 28 Sept 2026
  • LowCVE-2026-6062Mattermost doesn't validate channel ownership of an existing subscription before applying edits in github.com/mattermost/mattermost-server · 28 Sept 2026
All 478 advisories for github.com/mattermost/mattermost-server

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.