CVE-2026-3108
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMattermost versions 11.2.x <= 11.2.2, 10.11.x <= 10.11.10, 11.4.x <= 11.4.0, 11.3.x <= 11.3.1 fail to sanitize user-controlled post content in the mmctl commands terminal output which allows attackers to manipulate administrator terminals via crafted messages containing ANSI and OSC escape sequences that enable screen manipulation, fake prompts, and clipboard hijacking.. Mattermost Advisory ID: MMSA-2026-00599
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMattermost fails to sanitize ANSI and OSC escape sequences from user-controlled post content when displayed through the mmctl command-line interface. Attackers who can post messages can inject terminal escape codes to manipulate screen output, create fake prompts, and hijack clipboard operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 10.11.0, < 10.11.11>= 11.2.0, < 11.2.3>= 11.3.0, < 11.3.2= 11.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Mattermost Server installation and versionRun 'mattermost version' or check the Mattermost installation directory for version information. On Linux, this may be in /opt/mattermost or via a package manager query like 'dpkg -l mattermost-server'.Affected if The installed version falls within >= 10.11.0, < 10.11.11; >= 11.2.0, < 11.2.3; >= 11.3.0, < 11.3.2; or = 11.4.0
-
Locate mmctl command-line toolCheck if mmctl is installed on the system. Common locations include /opt/mattermost/bin/mmctl, or run 'which mmctl' to find it in PATH. This tool is bundled with Mattermost Server installations.Affected if mmctl is present on the system and accessible to administrators who manage the Mattermost instance
-
Determine if mmctl is used to view post contentReview administrator workflows and logs to see if mmctl is used to retrieve, list, or display channel messages or posts. Check commands such as 'mmctl post list', 'mmctl channel messages', or similar post retrieval operations.Affected if Administrators use mmctl to view user-generated post content from channels
-
Check for terminal output rendering of post contentObserve whether mmctl output containing post messages is rendered in a terminal emulator. The vulnerability exploits terminal rendering of ANSI/OSC escape sequences.Affected if mmctl is used to display post content in a terminal window or console
You are affected if your Mattermost Server version is in the vulnerable ranges AND administrators use mmctl to view post content in a terminal, allowing malicious escape sequences from user messages to manipulate screen output or hijack clipboard contents.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.11.1111.2.311.3.2
Update Mattermost to a patched version beyond the affected releases. Until patched, avoid using mmctl in shared terminal sessions or consider piping output through a sanitization filter.
Mattermost Server 10.11.11 / 11.2.3 / 11.3.2 / 11.4.1 (depending on your current branch)
- Identify the currently running Mattermost Server version using system administration tools or the Mattermost system console
- Determine which version branch your current installation belongs to (10.11.x, 11.2.x, 11.3.x, or 11.4.x)
- For 10.11.x branches: upgrade to Mattermost Server version 10.11.11 or later
- For 11.2.x branches: upgrade to Mattermost Server version 11.2.3 or later
- For 11.3.x branches: upgrade to Mattermost Server version 11.3.2 or later
- For 11.4.0: upgrade to Mattermost Server version 11.4.1 or later
- After upgrading, verify the mmctl terminal output properly sanitizes user-controlled post content by testing with messages containing ANSI escape sequences
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3108 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3108 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data