DEV Community

CVE Reports
CVE Reports

Posted on • Originally published at cvereports.com

CVE-2026-31841: CVE-2026-31841: Raw Database Statement Exposure in Hyperterse MCP Search Tool

#security #cve #cybersecurity

CVE-2026-31841: Raw Database Statement Exposure in Hyperterse MCP Search Tool

Vulnerability ID: CVE-2026-31841
CVSS Score: 6.5
Published: 2026-03-12

Hyperterse versions 2.0.0 through 2.1.9 exhibit an information disclosure vulnerability (CWE-433) within the Model Context Protocol (MCP) server implementation. The search tool fails to sanitize internal tool representations before returning them to the client, leaking raw SQL database statements. This exposure provides attackers with deep insight into internal database schemas, table structures, and query logic, lowering the barrier for subsequent targeted attacks.

TL;DR

Hyperterse < 2.2.0 leaks internal SQL statements via the MCP search tool due to missing output sanitization, exposing database schema details to users and AI agents.

⚠️ Exploit Status: POC

Technical Details

  • Vulnerability Class: CWE-433: Unparsed Raw Web Content Delivery
  • Attack Vector: Network (MCP callTool via JSON RPC)
  • CVSS v3.1 Score: 6.5 (Medium)
  • Confidentiality Impact: Low (Database schema and queries)
  • Exploit Status: Proof of Concept Available
  • Authentication Required: None

Affected Systems

  • Hyperterse Framework
  • Hyperterse MCP Server
  • AI Agent Integrations using vulnerable Hyperterse backends
  • Hyperterse: >= 2.0.0, < 2.2.0 (Fixed in: 2.2.0)

Code Analysis

Commit: 1fdb947

Fix: Remove raw statement field from search hit map to prevent schema disclosure

Commit: efa4005

Security: Harden search index by restricting statement indexing to adapter-backed tools

Mitigation Strategies

  • Upgrade to patched software version
  • Implement strict Principle of Least Privilege for the database service account
  • Manual sanitization of tool definitions for environments unable to patch
  • Use handler-only tools in place of SQL adapters for sensitive endpoints

Remediation Steps:

  1. Identify all deployed instances of Hyperterse MCP framework versions 2.0.0 through 2.1.9.
  2. Download the version 2.2.0 binaries or update the dependency via the respective package manager.
  3. Restart the Hyperterse MCP server process to load the updated runtime logic.
  4. Verify the fix by submitting a callTool request to the search endpoint and confirming the absence of the statement field in the JSON response.

References

Read the full report for CVE-2026-31841 on our website for more details including interactive diagrams and full exploit analysis.

Top comments (0)