CVE-2025-20036
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 Mobile Apps versions <=2.22.0 fail to properly validate post props which allows a malicious authenticated user to cause a crash via a malicious post.
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 Mobile Apps versions 2.22.0 and earlier fail to properly validate post properties, allowing any authenticated user to craft a malicious post containing specially formatted props that trigger a crash (denial of service) when received by mobile clients.
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< 2.23.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
-
Check Mattermost Mobile App version on iOS devicesOpen the App Store, search for Mattermost, tap the app, and view the version number under the app name. Alternatively, go to Settings > Mattermost > Version in the app.Affected if Version displayed is 2.22.0 or earlier
-
Check Mattermost Mobile App version on Android devicesOpen the Google Play Store, search for Mattermost, tap the app, and view the version under the app name. Alternatively, go to Settings > About > Version in the app.Affected if Version displayed is 2.22.0 or earlier
-
Check Mattermost Mobile App version via mobile device management (MDM) or enterprise mobility managementIf devices are managed via MDM/EMM, query the installed application inventory for 'Mattermost' and retrieve the package/app version from the device fleet.Affected if Any managed devices show Mattermost Mobile version 2.22.0 or earlier
-
Verify server-side post filtering as a partial indicatorExamine Mattermost server configuration files (config.json) or check if a plugin/filter is active that sanitizes post props before delivery to mobile clients.Affected if No post props filtering is configured on the server AND mobile clients are running vulnerable versions
You are affected if any mobile device in your environment is running Mattermost Mobile App version 2.22.0 or earlier and can receive posts from other authenticated users.
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 · scoped2.23.0
Upgrade Mattermost Mobile Apps to version >2.22.0. As an interim control, the server could filter or sanitize post props before delivering them to mobile clients to block known malformed payloads.
Mattermost Mobile 2.23.0
- 1. Open the app store on your mobile device (App Store for iOS or Google Play Store for Android)
- 2. Search for 'Mattermost' or locate the Mattermost Mobile app
- 3. Update the app to version 2.23.0 or later
- 4. Verify the update was successful by checking the app version in Settings > About > Version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,568.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-20036 — 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-2025-20036 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