CVE-2026-2476 is a high-severity (CVSS 7.6) Information Exposure vulnerability in github.com/mattermost/mattermost-plugin-msteams. A fix is available for github.com/mattermost/mattermost-plugin-msteams — see the affected versions and patch details below.
MS Teams plugin sensitive config values not properly masked in support packets
Exploitation Status
No confirmed exploitation observed yet
- 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 CVE-2026-2476.
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-plugin-msteamsReal-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 Plugins versions <=2.0.3.0 fail to properly mask sensitive configuration values which allows an attacker with access to support packets to obtain original plugin settings via exported configuration data. Mattermost Advisory ID: MMSA-2026-00606
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost-plugin-msteams | all versions | 1.15.1-0.20260102165339-036c761bd3cbgo get github.com/mattermost/mattermost-plugin-msteams@v1.15.1-0.20260102165339-036c761bd3cb |
Affected Products
ms teamsmattermostDetection & 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-plugin-msteams, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost-plugin-msteams to 1.15.1-0.20260102165339-036c761bd3cb or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-2476 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2026-2476 in your dependencies?
Find it across Go, including transitive dependencies.