HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorKeep agent security open: sponsor a project, place a banner, or fund a security initiative.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 7387 mattermost doesnt require role management
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High · CVSS 8.8CVE-2026-7387GHSA-6HXM-W4HV-VGVW

Mattermost doesn't require role-management authorization when setting the scheme_admin flag on group syncable link and patch endpoints in github.com/mattermost/mattermost-serverCVE-2026-7387

Answer in brief

CVE-2026-7387 records a High severity (CVSS 8.8) vulnerability in Mattermost doesn't require role-management authorization when setting the scheme_admin flag on group syncable link and patch endpoints in github.com/mattermost/mattermost-server. The current sources do not mark it as known exploited. The current feed maps github.com/mattermost/mattermost-server (go), github.com/mattermost/mattermost-server (go), github.com/mattermost/mattermost-server (go), github.com/mattermost/mattermost-server (go) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Jun 12, 2026Updated Aug 26, 2026Source checked Oct 10, 2026First seen by HOL Aug 25, 2026Material review Aug 26, 2026
Upstream Advisory

Key facts

Risk
High · CVSS 8.8
Exploitation
Not marked as known exploited
Affected software
11 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps github.com/mattermost/mattermost-server (go), github.com/mattermost/mattermost-server (go), github.com/mattermost/mattermost-server (go), github.com/mattermost/mattermost-server (go) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
github.com/mattermost/mattermost-servergo=11.6.011.6.1
github.com/mattermost/mattermost-servergo>=11.5.0,<=11.5.411.5.5
github.com/mattermost/mattermost-servergo>=10.11.0,<=10.11.1510.11.17
github.com/mattermost/mattermost-servergo>=10.11.0+incompatible <10.11.17+incompatible >=11.5.0+incompatible <11.5.5+incompatible >=11.6.0+incompatible <11.6.1+incompatible10.11.17+incompatible, 11.5.5+incompatible, 11.6.1+incompatible
github.com/mattermost/mattermost-servergo>=11.6.0 <11.6.111.6.1
github.com/mattermost/mattermost-servergo>=11.5.0 <11.5.511.5.5
github.com/mattermost/mattermost-servergo>=10.11.0 <10.11.1710.11.17
github.com/mattermost/mattermost-server/v5go>=0Not reported
github.com/mattermost/mattermost-server/v6go>=0Not reported
github.com/mattermost/mattermost/server/v8go>=8.0.0-20250731163400-5b955468ea1e,<8.0.0-20260506065351-202d125afa878.0.0-20260506065351-202d125afa87
github.com/mattermost/mattermost/server/v8go>=8.0.0-20250731163400-5b955468ea1e <8.0.0-20260506065351-202d125afa878.0.0-20260506065351-202d125afa87

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for github.com/mattermost/mattermost-server, github.com/mattermost/mattermost-server, github.com/mattermost/mattermost-server.
  2. 2Review the reported fix. Update github.com/mattermost/mattermost-server to 11.6.1; github.com/mattermost/mattermost-server to 11.5.5; github.com/mattermost/mattermost-server to 10.11.17; github.com/mattermost/mattermost-server to 10.11.17+incompatible; github.com/mattermost/mattermost-server to 11.6.1; github.com/mattermost/mattermost-server to 11.5.5; github.com/mattermost/mattermost-server to 10.11.17; github.com/mattermost/mattermost/server/v8 to 8.0.0-20260506065351-202d125afa87; github.com/mattermost/mattermost/server/v8 to 8.0.0-20260506065351-202d125afa87 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Jun 12, 2026

    Evidence: source:ghsa:source_dates:source-dates:record

  2. Source modified

    Aug 26, 2026

    Evidence: source:ghsa:source_dates:source-dates:record

  3. First seen by HOL

    Aug 25, 2026

Sources and claim methodology

  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • Source referencemattermost.com
  • NVD vulnerability recordnvd.nist.gov
  • GitHub security advisorygithub.com
Upstream source description

Mattermost versions 11.6.x <= 11.6.1, 11.5.x <= 11.5.4, 10.11.x <= 10.11.15, 10.11.x <= 10.11.16 fail to require role-management authorization when setting the scheme_admin flag on group syncable link and patch endpoints, which allows a user with group-link permissions to escalate themselves and group members to team or channel admin via crafted API requests. Mattermost Advisory ID: MMSA-2026-00665

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • OWASP Coraza WAF: ProcessURI silently drops QUERY_STRING and ARGS_GET on URI parse failure — defense-in-depth bypass for non-net/http integrationsSame go ecosystem
  • OWASP Coraza WAF: JSON body processor: argument-limit truncation reopens an unbounded-depth gjson.Valid stack overflow (process crash)Same go ecosystem
  • OWASP Coraza WAF: Unbounded recursion in JSON response body processor causes CPU exhaustionSame go ecosystem
  • OWASP Coraza WAF: Resource exhaustion via deferred file handle accumulation in multipart body processorSame go ecosystem
  • ageLANServer: Unbounded JSON Array Allocation in AoE3 Cloud `getFileURL` Endpoint Leads to Remote Denial of ServiceSame go ecosystem
  • yopass Prometheus metrics middleware allows remote memory exhaustion through unbounded method labelsSame go ecosystem

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
Not reported
Source
GitHub Security Advisories
Source checked
Oct 10, 2026
References
18 linked sources
Open source record