Mattermost vulnerable to excessive memory consumption

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS

• CVE-2023-5969: 0.53% estimated exploitation activity in the next 30 days; percentile 44.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Mattermost fails to properly sanitize the request to /api/v4/redirectlocation allowing an attacker, sending a specially crafted request to /api/v4/redirectlocation, to fill up the memory due to caching large items.

Published by the source

6 Nov 2023, 18:30 UTC

Last modified by the source

23 Nov 2023, 01:40 UTC

Source last checked

26 Oct 2026, 15:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w496-f5qq-m58j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-5969

Advisory: Mattermost vulnerable to excessive memory consumption
IDs: CVE-2023-5969, GHSA-w496-f5qq-m58j
Record: https://patchnext.com/advisories/cve-2023-5969 (revision 1, source checked 26 Oct 2026, 15:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/mattermost/mattermost/server/v8 9.0.1, 8.1.3, 8.0.4; github.com/mattermost/mattermost-server/v6 7.8.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/mattermost/mattermost/server/v8: affected >= 8.0.0, < 8.0.4; >= 8.1.0, < 8.1.3; >= 9.0.0, <= 9.0.0; fixed in 8.1.3, 8.0.4, 9.0.1
- Go github.com/mattermost/mattermost-server/v6: affected < 7.8.12; fixed in 7.8.12

## Suggested inspection (read-only)
- Go github.com/mattermost/mattermost/server/v8: check the installed version with your package manager.
- Go github.com/mattermost/mattermost-server/v6: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/mattermost/mattermost/server/v8, github.com/mattermost/mattermost-server/v6.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w496-f5qq-m58j (GitHub-reviewed advisory GHSA-w496-f5qq-m58j lists affected ranges: Go github.com/mattermost/mattermost-server/v6 >=0 =8.0.0 =8.1.0 =9.0.0 <=9.0.0)

Commands are suggestions: review each one before running it.