CVE-2026-121458: Instatic AI & CMS Model Context Protocol (MCP) Content Read Tools Missing Authorization & Cross-Tenant Data Disclosure
A critical authorization failure in the Model Context Protocol (MCP) server endpoints of Instatic versions 0.0.12 through 0.0.20 exposes private drafts, unpublished records, and cross-tenant documents to low-privileged accounts possessing basic ai.chat and content.edit.own capabilities. Disclosed and cataloged as weaponized by VulnCheck on November 4, 2026, the vulnerability stems from missing object-level access control enforcement in the content_get_document and content_list_documents MCP tool handlers. While standard REST endpoints enforce user ownership, the MCP interface relies solely on coarse transport authentication, allowing connected LLM agents or malicious operators to enumerate and exfiltrate enterprise intellectual property without restriction. Hermes assigns an Agentic Security Score (HASS) of 88.
HERMES THREAT SCORE & AUTONOMOUS AI AGENT MCP AUTHORIZATION INTEGRITY EVALUATION
Target:Instatic MCP Server Content Read Tools (content_get_document & content_list_documents) CVE-2026-121458: Instatic AI & CMS Model Context Protocol (MCP) Content Read Tools Missing Authorization & Cross-Tenant Data DisclosureVULNERABILITY
Software platform affected by security vulnerabilities and agentic attack patterns.
๐ Why is this related? (Evidence & Provenance)
“Confirmed security vulnerability in Instatic AI & Static CMS Platform documented in Hermes dossier.”
- [vulnerability_report]
- [government_confirmation]CISA verified active exploitation in the wild and mandated federal remediation deadline in KEV entry. — Source: Cybersecurity & Infrastructure Security Agency (CISA): CISA Adds CVE-2026-59822 to Known Exploited Vulnerabilities Catalog (Reliability: VERY_HIGH)
1. Vulnerability Overview & Architectural Context
Section titled โ1. Vulnerability Overview & Architectural ContextโInstatic is an open-source static CMS and publishing platform tailored for AI-augmented workflows. It features a native Model Context Protocol (MCP) server daemon that exposes document management, template compilation, and editorial capabilities directly to frontier models and external autonomous coding agents (such as Claude Desktop, Cursor, or LangChain agents).
In Instatic architectures, users operate under capability-based access control flags:
ai.chat: Permits bidirectional conversations with local or remote LLM models via the MCP socket.content.edit.own: Restricts user write and read operations to records whereauthor_id == current_user.id.content.read.all: Reserved for administrators and editorial managers.
Under normal HTTP REST routing, accessing /api/v1/documents/:id evaluates whether the document is published, belongs to the requesting tenant, or whether the caller holds administrative permissions. However, in the MCP subsystem, tool handlers registered under the MCP JSON-RPC protocol failed to verify record ownership, exposing all documents across the instance.
2. Root Cause Analysis & Code Breakdown
Section titled โ2. Root Cause Analysis & Code BreakdownโThe vulnerability resides within the MCP tool dispatcher in src/server/mcp/tools/content.ts. When an agent invokes content_get_document or content_list_documents, the server extracts user identity from the MCP transport layer but fails to pass authorization filters down to the database ORM query builder.
// Vulnerable Implementation: src/server/mcp/tools/content.ts (prior to 0.0.21)export const registerContentTools = (server: McpServer, db: Database) => { // Tool: Retrieve a document by ID server.tool( "content_get_document", { documentId: z.string().uuid() }, async ({ documentId }, { session }) => { // Check only coarse capability: Does caller have AI chat rights? if (!session.hasCapability("ai.chat")) { throw new McpError(ErrorCode.Unauthorized, "Missing ai.chat capability"); }
// FLAW: Direct database fetch without author_id / organization_id predicate const doc = await db.documents.findUnique({ where: { id: documentId } });
if (!doc) { throw new McpError(ErrorCode.InvalidParams, "Document not found"); }
// Exposes raw content, draft status, and private metadata across tenants return { content: [{ type: "text", text: JSON.stringify(doc) }] }; } );
// Tool: List documents server.tool( "content_list_documents", { status: z.enum(["draft", "published", "archived"]).optional() }, async ({ status }, { session }) => { if (!session.hasCapability("ai.chat")) { throw new McpError(ErrorCode.Unauthorized, "Missing ai.chat capability"); }
// FLAW: Returns all documents across all users and organizations const query: any = {}; if (status) query.status = status;
const docs = await db.documents.findMany({ where: query, take: 100 }); return { content: [{ type: "text", text: JSON.stringify(docs) }] }; } );};The Fix in Version 0.0.21
Section titled โThe Fix in Version 0.0.21โIn Instatic 0.0.21, the development team introduced scoped session context validation, enforcing tenancy and ownership filters on every MCP query builder call:
// Patched Implementation: src/server/mcp/tools/content.ts (0.0.21)server.tool( "content_get_document", { documentId: z.string().uuid() }, async ({ documentId }, { session }) => { // Enforce both AI capability AND object-level read permissions if (!session.hasCapability("ai.chat")) { throw new McpError(ErrorCode.Unauthorized, "Missing ai.chat capability"); }
const whereClause: any = { id: documentId };
// If user cannot read all content, strictly restrict to own documents if (!session.hasCapability("content.read.all")) { whereClause.organizationId = session.organizationId; if (session.hasCapability("content.edit.own")) { whereClause.authorId = session.userId; } }
const doc = await db.documents.findFirst({ where: whereClause }); if (!doc) { throw new McpError(ErrorCode.InvalidParams, "Document not found or access denied"); }
return { content: [{ type: "text", text: JSON.stringify(doc) }] }; });3. Attack Vector & Exploitation Flow
Section titled โ3. Attack Vector & Exploitation FlowโsequenceDiagram autonumber actor Attacker as Low-Privileged Attacker (ai.chat) participant Client as MCP Client / AI Chat Client participant MCPServer as Instatic MCP Daemon (JSON-RPC) participant DB as System SQLite / Postgres DB participant Victim as Target Organization / CEO Drafts
Victim->>DB: Stores confidential strategy document (status: 'draft') Attacker->>Client: Establishes MCP session with low-priv token Client->>MCPServer: {"jsonrpc": "2.0", "method": "tools/call", "params": {"name": "content_list_documents", "arguments": {"status": "draft"}}} MCPServer->>MCPServer: Verifies session.hasCapability("ai.chat") -> TRUE Note over MCPServer,DB: Missing WHERE author_id check! MCPServer->>DB: SELECT * FROM documents WHERE status = 'draft' DB-->>MCPServer: Returns all private drafts across all tenants MCPServer-->>Client: Returns JSON containing unreleased docs and secret tokens Attacker->>Client: Exfiltrates proprietary dataThe attack can be performed either through direct JSON-RPC calls over the WebSocket/stdio MCP interface or via indirect prompt injection. An attacker embedding hidden instructions inside a public forum or shared markdown file can direct an autonomous agent acting on behalf of a user to run content_list_documents and transmit the results to an external telemetry webhook.
4. Forensic Investigation & Threat Hunting
Section titled โ4. Forensic Investigation & Threat HuntingโSigma Rule: Detection of Unscoped MCP Document Enumeration
Section titled โSigma Rule: Detection of Unscoped MCP Document Enumerationโtitle: Suspicious MCP Document Cross-Tenant Enumerationid: e8a9142e-1823-41bb-a794-d2c676231201status: experimentaldescription: Detects rapid enumeration of unpublished drafts and cross-tenant documents via Instatic MCP tools.references: - https://vulncheck.com/advisories/instatic-before-authorization-bypass-via-mcp-content-read-toolsauthor: Hermes Codex Cyber Threat Intelligencedate: 2026-11-04logsource: category: application product: instaticdetection: selection_mcp_call: mcp.method: 'tools/call' mcp.tool_name|in: - 'content_list_documents' - 'content_get_document' selection_low_priv: user.role|in: - 'contributor' - 'external_editor' - 'ai_chat_user' filter_admin: user.role: 'admin' condition: selection_mcp_call and selection_low_priv and not filter_adminfields: - user.id - user.role - mcp.tool_name - mcp.argumentsfalsepositives: - Legitimate editorial automation running under dedicated service accounts.level: high// Azure Sentinel / Microsoft Defender Hunting Query// Detects low-privilege MCP API calls accessing multiple distinct author document recordsInstaticAuditLogs_CL| where TimeGenerated >= ago(24h)| where Protocol_s == "MCP-JSONRPC"| where ToolName_s in ("content_get_document", "content_list_documents")| where UserRole_s !in ("administrator", "superadmin")| extend RequestedDocId = tostring(parse_json(Arguments_s).documentId)| summarize DistinctDocsAccessed = dcount(RequestedDocId), RequestCount = count(), DocList = make_set(RequestedDocId) by UserId_s, UserRole_s, bin(TimeGenerated, 15m)| where DistinctDocsAccessed > 10| project TimeGenerated, UserId_s, UserRole_s, DistinctDocsAccessed, RequestCount, DocList# PowerShell script to inspect local Instatic audit logs for unauthorized MCP tool invocationsGet-Content -Path "C:\ProgramData\Instatic\logs\mcp-audit.log" -Tail 5000 | ConvertFrom-Json | Where-Object { $_.tool_name -eq "content_get_document" -or $_.tool_name -eq "content_list_documents"} | Group-Object -Property user_id | ForEach-Object { [PSCustomObject]@{ UserId = $_.Name TotalCalls = $_.Count TargetDocs = ($_.Group | Select-Object -ExpandProperty arguments -ErrorAction SilentlyContinue | Measure-Object).Count }} | Format-Table -AutoSizeActionable Indicators of Compromise (IOCs)
Section titled โActionable Indicators of Compromise (IOCs)โ| Indicator Type | Observable / Indicator | Role / Context | Status |
|---|---|---|---|
| MCP Tool Method | content_get_document, content_list_documents | Target tool endpoints invoked with cross-tenant arguments | ACTIVE |
| Tool Arguments | documentId pointing to foreign author rows | Object-level authorization bypass observable | MALICIOUS |
| Audit Alert | mcp-server: 'Access denied: document owner mismatch' | Log signature generated by post-patch enforcement | CONFIRMED |
| Traffic Anomaly | Spikes in JSON-RPC tools/call requests from low-privilege sessions | Bulk exfiltration or automated enumeration wave | ANOMALOUS |
5. Remediation Strategy & Mitigation Guidance
Section titled โ5. Remediation Strategy & Mitigation GuidanceโVersion Matrix & Patch Engineering
Section titled โVersion Matrix & Patch EngineeringโThe maintainers resolved this vulnerability in Instatic version 0.0.21 by updating packages/mcp-server/src/tools/content.ts. The patch binds document read queries strictly to the callerโs verified session.userId and tenancy boundary, throwing an authorization fault when foreign IDs are queried:
| Product Branch | Vulnerable Versions | Fixed Release | Patch Status |
|---|---|---|---|
| Instatic 0.0.x | 0.0.12 โ 0.0.20 | 0.0.21 | Official Security Release |
| Instatic < 0.0.12 | < 0.0.12 | N/A (MCP absent) | Upgrade to 0.0.21 Recommended |
- Upgrade Instatic Daemon: Immediately update Instatic to version
0.0.21or later. Verify that the running server binary reportsinstatic --version>=0.0.21. - Restrict MCP Tool Exposure: In
instatic.config.json, disable MCP tool exposure to non-administrative users by settingmcp.allow_public_tools: falseand binding MCP listeners exclusively to localhost (127.0.0.1) or an authenticated Unix domain socket. - Audit Historical Tool Access: Query system audit tables for
content_get_documentandcontent_list_documentscalls initiated by non-administrative users between 2026-10-01 and the patch date to identify potential exfiltration of sensitive unpublished materials. - Enforce Agentic Role-Based Scoping: Ensure that AI agent integrations utilize ephemeral, scoped service principal tokens rather than standing user session cookies.