Skip to content
Fencer Intel
low 3.1

CVE-2026-4053 json

post edit time limit is not enforced on some post update operations

published 5mo ago modified 4mo ago also GHSA-hw87-6jcq-9f8q , GO-2026-5442 , EUVD-2026-30586

cvss
3.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 5%
public exploits
0
none known

Summary

Mattermost versions 11.5.x <= 11.5.1, 10.11.x <= 10.11.13 fail to enforce the PostEditTimeLimit on non-message post fields which allows an authenticated user to modify post file attachments, props, and pin status after the edit window has expired via the post patch and update API endpoints.. Mattermost Advisory ID: MMSA-2026-00631

Patch / fix

  • go github.com/mattermost/mattermost-server 0.0.0-20260414103857-b21ef302025e, 11.5.2, 11.5.2+incompatible
  • Mattermost Mattermost 10.11.14, 11.5.2, 11.6.0
  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Is CVE-2026-4053 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
GitHub 3.1 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/mattermost/mattermost-server
>=11.5.0, <11.5.2
>=0.0.0-20250731163400-5b955468ea1e, <0.0.0-20260414103857-b21ef302025e
>=11.5.0+incompatible, <11.5.2+incompatible
11.5.2
0.0.0-20260414103857-b21ef302025e
11.5.2+incompatible

Affected products

  • Mattermost Mattermost

Classification

Weakness
  • CWE-672 Operation on a Resource after Expiration or Release

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.