Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
41 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Go github.com/mattermost/mattermost-server/v6 < 5.3.2-0.20250815165020-c8d66301415d
Fixed in
5.3.2-0.20250815165020-c8d66301415d· Vendor fix available
Issue
Mattermost versions < 11 fail to properly restrict access to archived channel search API which allows guest users to discover archived public channels via the /api/v4/teams/{teamid}/channels/searcharchived endpoint
Recommended action: Upgrade to 5.3.2-0.20250815165020-c8d66301415d (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 5.3.2-0.20250905150616-ba86dfc5876b
Fixed in
5.3.2-0.20250905150616-ba86dfc5876b· Vendor fix available
Issue
Mattermost versions 10.11.x <= 10.11.3, 10.5.x <= 10.5.11 fail to properly validate team membership permissions in the Add Channel Member API, which allows users from one team to access user metadata and channel membership information from other teams via the API endpoint.
Recommended action: Upgrade to 5.3.2-0.20250905150616-ba86dfc5876b (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 6.0.0-20240626164322-c758cecaf30c
Fixed in
6.0.0-20240626164322-c758cecaf30c· Vendor fix available
Issue
Mattermost versions 9.9.x <= 9.9.0, 9.5.x <= 9.5.6 fail to properly restrict channel creation which allows a malicious remote to create arbitrary channels, when shared channels were enabled.
Recommended action: Upgrade to 6.0.0-20240626164322-c758cecaf30c (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 0.0.0-20240209181221-674f549daf0e
Fixed in
0.0.0-20240209181221-674f549daf0e· Vendor fix available
Issue
Resource Exhaustion in Mattermost Server versions 8.1.x before 8.1.10 fails to limit the size of the payload that can be read and parsed allowing an attacker to send a very large email payload and crash the server.
Recommended action: Upgrade to 0.0.0-20240209181221-674f549daf0e (pre-release) or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 <= 7.8.9
Fixed in
7.8.10· Vendor fix available
Issue
Mattermost fails to properly verify the permissions needed for viewing archived public channels, allowing a member of one team to get details about the archived public channels of another team via the GET /api/v4/teams/<team-id/channels/deleted endpoint.
Recommended action: Upgrade to 7.8.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 <= 8.1.6
Fixed in
8.1.7· Vendor fix available
Issue
Mattermost fails to scope the WebSocket response around notified users to a each user separately resulting in the WebSocket broadcasting the information about who was notified about a post to everyone else in the channel.
Recommended action: Upgrade to 8.1.7 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.14
Fixed in
7.8.14· Vendor fix available
Issue
Mattermost webapp fails to validate route parameters in/<TEAMNAME/channels/<CHANNELNAME allowing an attacker to perform a client-side path traversal.
Recommended action: Upgrade to 7.8.14 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.14
Fixed in
7.8.14· Vendor fix available
Issue
Mattermost is grouping calls in the /metrics endpoint by id and reports that id in the response. Since this id is the channelID, the public /metrics endpoint is revealing channelIDs.
Recommended action: Upgrade to 7.8.14 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.13
Fixed in
7.8.13· Vendor fix available
Issue
Mattermost fails to limit the log size of server logs allowing an attacker sending specially crafted requests to different endpoints to potentially overflow the log.
Recommended action: Upgrade to 7.8.13 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.13
Fixed in
7.8.13· Vendor fix available
Issue
Mattermost fails to perform proper authorization in the /plugins/focalboard/api/v2/users endpoint allowing an attacker who is a guest user and knows the ID of another user to get their information (e.g. name, surname, nickname) via Mattermost Boards.
Recommended action: Upgrade to 7.8.13 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.13
Fixed in
7.8.13· Vendor fix available
Issue
Mattermost fails to check if hardened mode is enabled when overriding the username and/or the icon when posting a post. If settings allowed integrations to override the username and profile picture when posting, a member could also override the username and icon when making a post even if the Hardened Mode setting was enabled
Recommended action: Upgrade to 7.8.13 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.13
Fixed in
7.8.13· Vendor fix available
Issue
Mattermost fails to properly validate the "Show Full Name" option in a few endpoints in Mattermost Boards, allowing a member to get the full name of another user even if the Show Full Name option was disabled.
Recommended action: Upgrade to 7.8.13 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.13
Fixed in
7.8.13· Vendor fix available
Issue
Mattermost fails to use innerText / textContent when setting the channel name in the webapp during autocomplete, allowing an attacker to inject HTML to a victim's page by create a channel name that is valid HTML. No XSS is possible though.
Recommended action: Upgrade to 7.8.13 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.13
Fixed in
7.8.13· Vendor fix available
Issue
Mattermost fails to limit the amount of data extracted from compressed archives during board import in Mattermost Boards allowing an attacker to consume excessive resources, possibly leading to Denial of Service, by importing a board using a specially crafted zip (zip bomb).
Recommended action: Upgrade to 7.8.13 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.13
Fixed in
7.8.13· Vendor fix available
Issue
Mattermost fails to check whether the "Allow users to view archived channels" setting is enabled during permalink previews display, allowing members to view permalink previews of archived channels even if the "Allow users to view archived channels" setting is disabled.
Recommended action: Upgrade to 7.8.13 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.13
Fixed in
7.8.13· Vendor fix available
Issue
Mattermost fails to properly check a redirect URL parameter allowing for an open redirect was possible when the user clicked "Back to Mattermost" after providing a invalid custom url scheme in /oauth/{service}/mobilelogin?redirectto=
Recommended action: Upgrade to 7.8.13 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.13
Fixed in
7.8.13· Vendor fix available
Issue
Mattermost fails to properly limit the characters allowed in different fields of a block in Mattermost Boards allowing a attacker to consume excessive resources, possibly leading to Denial of Service, by patching the field of a block using a specially crafted string.
Recommended action: Upgrade to 7.8.13 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.12
Fixed in
7.8.12· Vendor fix available
Issue
Mattermost fails to properly validate requests to the Calls plugin, allowing an attacker sending a request without a User Agent header to cause a panic and crash the Calls plugin
Recommended action: Upgrade to 7.8.12 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.12
Fixed in
7.8.12· Vendor fix available
Issue
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.
Recommended action: Upgrade to 7.8.12 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 >= 5.4.0-rc1, < 7.8.12; < 5.3.2-0.20230825233148-f787fd63368a
Fixed in
5.3.2-0.20230825233148-f787fd63368a7.8.12· Vendor fix available
Issue
Mattermost fails to properly sanitize the user object when updating the username, resulting in the password hash being included in the response body.
Recommended action: Upgrade to 7.8.12 or 5.3.2-0.20230825233148-f787fd63368a (pre-release) by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.10
Fixed in
7.8.10· Vendor fix available
Issue
Mattermost fails to properly check permissions when retrieving a post allowing for a System Role with the permission to manage channels to read the posts of a DM conversation.
Recommended action: Upgrade to 7.8.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.10
Fixed in
7.8.10· Vendor fix available
Issue
Mattermost fails to enforce character limits in all possible notification props allowing an attacker to send a really long value for a notificationprop resulting in the server consuming an abnormal quantity of computing resources and possibly becoming temporarily unavailable for its users.
Recommended action: Upgrade to 7.8.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.10
Fixed in
7.8.10· Vendor fix available
Issue
Mattermost fails to properly validate permissions when demoting and deactivating a user allowing for a system/user manager to demote / deactivate another manager
Recommended action: Upgrade to 7.8.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.10
Fixed in
7.8.10· Vendor fix available
Issue
Mattermost fails to properly verify the permissions when managing/updating a bot allowing a User Manager role with user edit permissions to manage/update bots.
Recommended action: Upgrade to 7.8.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Go github.com/mattermost/mattermost-server/v6 < 7.8.10
Fixed in
7.8.10· Vendor fix available
Issue
Mattermost fails to properly validate the permissions when soft deleting a team allowing a team member to soft delete other teams that they are not part of
Recommended action: Upgrade to 7.8.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.