Mattermost Fails to Lockout LDAP Users After Repeated Login FailuresGHSA-qgwx-rffp-6cx9
MEDIUMFix: mattermost/mattermost#30821GHSA-qgwx-rffp-6cx9 is a medium-severity (CVSS 5.8) CWE-645 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.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-qgwx-rffp-6cx9.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8Real-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.6.x <= 10.6.1, 10.5.x <= 10.5.2, 10.4.x <= 10.4.4, 9.11.x <= 9.11.11 fail to lockout LDAP users following repeated login failures, which allows attackers to lock external LDAP accounts through repeated login failures through Mattermost.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 10.6.0&&< 10.6.2 | 10.6.2go get github.com/mattermost/mattermost/server/v8@v10.6.2 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 10.5.0&&< 10.5.3 | 10.5.3go get github.com/mattermost/mattermost/server/v8@v10.5.3 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 10.4.0&&< 10.4.5 | 10.4.5go get github.com/mattermost/mattermost/server/v8@v10.4.5 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 9.11.0&&< 9.11.12 | 9.11.12go get github.com/mattermost/mattermost/server/v8@v9.11.12 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | all versions | 8.0.0-20250415054241-76ab3867b785go get github.com/mattermost/mattermost/server/v8@v8.0.0-20250415054241-76ab3867b785 |
Affected Products
mattermost servermattermostDetection & mitigation playbook
Open-source dependencyDetect
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.
Fix
Update github.com/mattermost/mattermost/server/v8 to 10.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qgwx-rffp-6cx9 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.
Frequently Asked Questions
Is GHSA-qgwx-rffp-6cx9 in your dependencies?
Find it across Go, including transitive dependencies.