CVE-2026-19541: Outgoing OAuth connection client secret exposure during connection validation

Published Oct 16, 2026
·
Updated

Mattermost versions 11.9.x <= 11.9.1, 11.8.x <= 11.8.5, 11.7.x <= 11.7.10, 11.10.x <= 11.10.1 fail to require re-entry of the stored client secret when validating an outgoing OAuth connection, which allows an authenticated user with permission to manage outgoing OAuth connections to obtain the secret via pointing the token URL at an attacker-controlled endpoint and triggering validation.. Mattermost Advisory ID: MMSA-2026-00761

Affected Software

5 affected components
Mattermost Mattermost<=11.9.1, <=11.8.5, <=11.7.10, <=11.10.1
Mattermost Mattermost Server>=11.7.0<11.7.11
Mattermost Mattermost Server>=11.8.0<11.8.6
Mattermost Mattermost Server>=11.9.0<11.9.2
Mattermost Mattermost Server>=11.10.0<11.10.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Mattermost to a version that resolves this vulnerability.

    Patch MMSA-2026-00761

Event History

Oct 16, 2026
CVE Published
via MITRE·06:54 AM
Data Sourced
via MITRE·06:54 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·07:17 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Who can exploit this issue?

An attacker must be authenticated and have permission to manage outgoing OAuth connections. They also need to be able to modify an outgoing OAuth connection's token URL and trigger connection validation.

2

What is exposed if exploitation succeeds?

The stored client secret for the outgoing OAuth connection can be sent to an attacker-controlled endpoint during validation. The issue affects confidentiality only; the provided vector does not indicate integrity or availability impact.

3

Are all Mattermost deployments affected by default?

Exploitation depends on an outgoing OAuth connection with a stored client secret and on a user having permission to manage outgoing OAuth connections. The provided information does not establish whether such connections or permissions exist in a default deployment.

4

What can be done before updating?

Restrict the permission to manage outgoing OAuth connections to trusted administrators. Review and limit who can change token URLs or initiate validation for these connections.

5

How can administrators assess whether they may be affected?

Check whether the deployment runs Mattermost 11.9.x through 11.9.1, 11.8.x through 11.8.5, 11.7.x through 11.7.10, or 11.10.x through 11.10.1. Also identify outgoing OAuth connections with stored client secrets and users who can manage or validate them.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203