How severe is CVE-2026-4273?

CVE-2026-4273 has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-4273?

CVE-2026-4273 affects the following packages: github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost-server (Go). Ecosystems affected: Go.

How do I fix CVE-2026-4273?

Update github.com/mattermost/mattermost/server/v8 to 11.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-4273 is resolved across your whole dependency graph.

How do I detect CVE-2026-4273 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost/server/v8, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-4273 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2026-4273 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-4273 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-4273?

CVE-2026-4273 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 13th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-4273?

CVE-2026-4273 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-4273 published, and has it been updated?

CVE-2026-4273 was published on May 18, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

LOW severity

CVE-2026-4273 — v8

LOWFix: mattermost/mattermost@742e0be

CVE-2026-4273 is a low-severity (CVSS 3.7) CWE-863 vulnerability in github.com/mattermost/mattermost/server/v8. A fix is available for github.com/mattermost/mattermost/server/v8 — see the affected versions and patch details below.

Insufficient token rotation validation in remote cluster invite confirmation

Also known asGHSA-hqpj-f3jh-29vxGO-2026-5432

Published

May 18, 2026

Updated

Aug 12, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Sep 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-4273.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs13th percentile — riskier than 13% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-4273 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 380,526 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

4 pkgs affected

🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Mattermost versions 11.5.x <= 11.5.1, 10.11.x <= 10.11.13 fail to validate that the RefreshedToken differs from the original invite token during remote cluster invite confirmation which allows an authenticated attacker to bypass token rotation and reuse the original invite token via sending a crafted invite confirmation with a RefreshedToken matching the original token. Mattermost Advisory ID: MMSA-2026-00575

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 11.5.0&&< 11.5.2	11.5.2`go get github.com/mattermost/mattermost/server/v8@v11.5.2`
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 10.11.0&&< 10.11.14	10.11.14`go get github.com/mattermost/mattermost/server/v8@v10.11.14`
🐹Go	`github.com/mattermost/mattermost/server/v8`	all versions	8.0.0-20260313190740-742e0be95074`go get github.com/mattermost/mattermost/server/v8@v8.0.0-20260313190740-742e0be95074`
🐹Go	`github.com/mattermost/mattermost-server`	all versions	5.3.2-0.20260313190740-742e0be95074`go get github.com/mattermost/mattermost-server@v5.3.2-0.20260313190740-742e0be95074`

Affected Products

1 product · 2 configurations

Application

mattermost servermattermost

≥ 11.5.0 && < 11.5.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost/server/v8, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost/server/v8 to 11.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-4273 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-4273 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

3.7/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

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

CWE Classification

CWE-863CWE-863

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

May 18, 2026

Last updated

Aug 12, 2026

Identifiers

CVE-2026-4273

GHSA-hqpj-f3jh-29vx

GO-2026-5432

References

Advisorygithub.com Advisorymattermost.com Advisorynvd.nist.gov Webgithub.com Packagegithub.com

Related vulnerabilities

This CVE is low severity; 8 of 8 other CVEs affecting v8 are rated as high or higher (top: high).

CVE-2026-6046CVE-2026-7387CVE-2026-6961CVE-2026-7184CVE-2026-6689CVE-2026-6739CVE-2026-3433CVE-2026-4915

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 12, 2026

CVE-2026-4273 — v8

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2026-4273 in your dependencies?