Improper file ownership validation in the Boards API allows unauthorised file access
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: github.com/mattermost/mattermost-server (Go) 10.11.15, 10.11.15+incompatible, 11.4.5.
Low priority for now. Upgrade to github.com/mattermost/mattermost-server (Go) 10.11.15, 10.11.15+incompatible, 11.4.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Mattermost versions 11.6.x <= 11.6.0, 11.5.x <= 11.5.3, 11.4.x <= 11.4.4, 10.11.x <= 10.11.14 fail to validate file ownership and access control, which allows an authenticated user to access and download files belonging to other users or teams via crafted Boards API requests using valid file IDs.. Mattermost Advisory ID: MMSA-2026-00620
- Published
- May 22, 2026
- Updated
- Jul 23, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-639
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.1
- CNA · Mattermost
- 5.9
- 1.2 point gap
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| mattermost | mattermost server | cpe:2.3:a:mattermost:mattermost_server |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- mattermost mattermost server10.11.0 and later · before 10.11.15
- mattermost mattermost server11.4.0 and later · before 11.4.5
- mattermost mattermost server11.5.0 and later · before 11.5.4
- mattermost mattermost server11.6.0 and later · before 11.6.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Mattermost). Independent of NVD's CPE analysis and usually ahead of it.
Mattermost Mattermost
- 11.7.0, 11.6.1, 11.5.4, 11.4.5, 10.11.15not affected
- 11.6.0 and later · up to and including 11.6.0affected · semver
- 11.5.0 and later · up to and including 11.5.3affected · semver
- 11.4.0 and later · up to and including 11.4.4affected · semver
- 10.11.0 and later · up to and including 10.11.14affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/mattermost/mattermost-server | from 10.11.0 · before 10.11.15 | 10.11.15 |
| Go | github.com/mattermost/mattermost-server | from 10.11.0+incompatible · before 10.11.15+incompatible | 10.11.15+incompatible |
| Go | github.com/mattermost/mattermost-server | from 11.4.0 · before 11.4.5 | 11.4.5 |
| Go | github.com/mattermost/mattermost-server | from 11.4.0+incompatible · before 11.4.5+incompatible | 11.4.5+incompatible |
| Go | github.com/mattermost/mattermost-server | from 11.5.0 · before 11.5.4 | 11.5.4 |
| Go | github.com/mattermost/mattermost-server | from 11.5.0+incompatible · before 11.5.4+incompatible | 11.5.4+incompatible |
| Go | github.com/mattermost/mattermost-server | from 11.6.0 · before 11.6.1 | 11.6.1 |
| Go | github.com/mattermost/mattermost-server | from 11.6.0+incompatible · before 11.6.1+incompatible | 11.6.1+incompatible |
Same product
mattermost: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-4858Path traversal in integration action URL leading to arbitrary API execution via system admin’s auth token.39Monitor
- CVE-2025-12421Account Takeover via Code Exchange Endpoint39Monitor
- CVE-2025-12419Account takeover on OAuth/OpenID-enabled servers39Monitor
- CVE-2025-4981Path Traversal Leading to RCE by Any Authenticated Mattermost User39Monitor
- CVE-2023-6458Client side path traversal due to lack of route parameters validation39Monitor
- CVE-2017-18920An issue was discovered in Mattermost Server before 3.6.2.39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/mattermost/mattermost-server | 10.11.15 | Package registry (OSV) |
| Go:github.com/mattermost/mattermost-server | 10.11.15+incompatible | Package registry (OSV) |
| Go:github.com/mattermost/mattermost-server | 11.4.5 | Package registry (OSV) |
| Go:github.com/mattermost/mattermost-server | 11.4.5+incompatible | Package registry (OSV) |
| Go:github.com/mattermost/mattermost-server | 11.5.4 | Package registry (OSV) |
| Go:github.com/mattermost/mattermost-server | 11.5.4+incompatible | Package registry (OSV) |
| Go:github.com/mattermost/mattermost-server | 11.6.1 | Package registry (OSV) |
| Go:github.com/mattermost/mattermost-server | 11.6.1+incompatible | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- eahmedfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-9812115 days apartMissing property field ownership validation in Playbooks run property update endpoint26Monitor
- CVE-2025-9081245 days apartIDOR in board file download allows any user to download any file by UUID26Monitor
- CVE-2026-606231 days apartIDOR in Jira plugin subscription edit endpoint25Monitor
- CVE-2026-970852 days apartIncoming webhook user attribution via unvalidated webhook owner19Monitor
- CVE-2026-1010352 days apartAuthenticated remote cluster can modify or delete posts it does not own in Mattermost Connected Workspaces shared channels17Monitor
- CVE-2026-654152 days apartUnscoped updates to other playbooks' metric configuration17Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-639 · Authorization Bypass Through User-Controlled KeyCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
nvd-primary
Root cause
The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.
The bug in code
The whole CWE-639 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const invoice = await Invoice.findById(req.params.id);res.json(invoice);Fixed
const invoice = await Invoice.findOne({ id: req.params.id, ownerId: req.user.id,});if (!invoice) return res.sendStatus(404);res.json(invoice);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.