dbcve.org
Mattermost MobileApplication · Mattermost

CVE-2025-30516

HIGH · 7.5 CVSS v3.1 Published 2025-04-14
Fix available
A fix is available. Upgrade to 2.26.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Mattermost Mobile Apps versions <=2.25.0  fail to terminate sessions during logout under certain conditions (e.g. poor connectivity), allowing unauthorized users on shared devices to access sensitive notification content via continued mobile notifications

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 confidence

Mattermost Mobile Apps versions 2.25.0 and earlier fail to properly terminate user sessions during logout, particularly under poor network connectivity conditions. This session termination failure allows the app to continue receiving and displaying sensitive notifications on shared devices after the nominal logout, exposing notification content to unauthorized subsequent users of the device.

MitigationOrganizations should enforce additional session controls server-side and consider implementing remote session invalidation capabilities. Users of affected versions should update to a patched version once available and should be advised to manually clear app data on shared devices as a precautionary measure.

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
Mattermost MobileApplication
Affected:< 2.26.0

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Mattermost Mobile version
    On iOS: Settings > Apps > Mattermost > Version. On Android: Settings > Apps > Mattermost > App info > Version. Compare the displayed version number to the affected range (versions before 2.26.0).
    Affected if The installed version is 2.25.0 or earlier, or any version listed below 2.26.0.
  2. Confirm notification configuration is active
    Verify that push notifications are enabled in the app: Open Mattermost Mobile > tap profile icon > Settings > Notifications > Push Notifications is turned ON.
    Affected if Notifications are enabled and the app version is vulnerable.
  3. Assess shared device usage
    Determine whether the mobile device is shared among multiple users, or could be accessed by other individuals after logout.
    Affected if The device is or could be used by multiple users, and the app version is vulnerable.
  4. Test logout behavior under poor network conditions
    Enable airplane mode or severely restrict network connectivity, then attempt to log out of the Mattermost Mobile app. After logout, observe whether the app continues to receive or display push notifications.
    Affected if After logging out with limited connectivity, notifications continue to appear on the device.

A user is affected if they are running Mattermost Mobile version 2.25.0 or earlier, have notifications enabled, and use or may use shared devices where logout may occur under poor network conditions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.26.0 or later
Fixed in 2.26.0
Interim mitigation

Organizations should enforce additional session controls server-side and consider implementing remote session invalidation capabilities. Users of affected versions should update to a patched version once available and should be advised to manually clear app data on shared devices as a precautionary measure.

Recommended fix High confidence

2.26.0

  1. Upgrade Mattermost Mobile App to version 2.26.0 or later from your device's app store

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mattermost Mobile Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30516 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30516 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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