Security researchers have identified a critical blind spot in enterprise AI deployments: the Model Context Protocol (MCP) server layer that connects AI agents to external tools remains largely untracked and unprotected.
In a September report titled MCP security September 2026: Deadbugz + 3 server CVEs, Adversa AI detailed 68 vulnerabilities discovered across audited MCP servers. The AI Governance Institute followed with an analysis labeling the problem a systemic gap. Earlier data from the same researchers showed that 91.8% of examined MCP servers lacked OAuth authentication entirely.
Four Vulnerability Classes with Direct Impact
The report categorized the flaws into four well-known but newly dangerous classes in the MCP context:
- SQL injection allowing attackers to read backend databases through tool calls.
- Server-side request forgery (SSRF) specifically targeting cloud metadata services to steal temporary credentials.
- Prompt template injection that manipulates AI agents into executing attacker-chosen actions.
- Path traversal enabling unauthorized file access.
Each class has already led to data exfiltration or full agent compromise in production environments.
Additional research on 19 MCP servers revealed that tool outputs routinely inject unexpected instructions into the AI context. Context7 was specifically flagged for prompt injection issues, and Digital Applied confirmed similar behavior in its audit.
Approval Workflows and Logging at Risk
A September 4 disclosure highlighted a command classification flaw in an SSH MCP server implementation that allowed a high-privilege command to be mislabeled as safe, undermining read-only approval assumptions. Audit logs themselves become unreliable once an agent processes attacker-controlled content.
On September 10, the Cloud Security Alliance updated its guidelines, requiring OAuth 2.1 + PKCE and mandatory server metadata validation before any remote MCP connection. The guidance explicitly criticizes weak server discovery and blind trust in endpoints.
Immediate Actions Recommended
Security teams are advised to:
- Inventory all MCP servers and add them to asset management systems.
- Scan for the four vulnerability classes without sampling.
- Isolate MCP processes from cloud metadata endpoints.
- Update vendor questionnaires to cover authentication and input validation.
- Feed MCP-related CVEs into existing monitoring and watch for CISA KEV listings.
- Measure deployments against OWASP GenAI and MCP sandbox baselines.
The 68 vulnerabilities will not disappear without action. Organizations must now determine ownership of the MCP layer that currently sits outside every existing inventory and questionnaire.
