CVE-2026-31841 Details
Description
Hyperterse is a tool-first MCP framework for building AI-ready backend surfaces from declarative config. Prior to v2.2.0, the search tool allows LLMs to search for tools using natural language. While returning results, Hyperterse also returned the raw SQL queries, exposing statements which were supposed to be executed under the hood, and protected from being displayed publicly. This issue has been fixed as of v2.2.0.
A vulnerability in Hyperterse versions 2.0.0 prior to 2.2.0 allows the search tool to expose raw SQL queries to users. This exposure includes database statements that were intended to be executed privately, creating a potential risk by revealing underlying query details. The issue has been addressed in version 2.2.0.
Users can upgrade to Hyperterse version 2.2.0 to address this vulnerability. Instructions for updating can be found in the Hyperterse GitHub repository.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Mar 12, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/hyperterse/hyperterse/releases/tag/v2.2.0 | [email protected] | ProductRelease Notes |
| https://github.com/hyperterse/hyperterse/security/advisories/GHSA-92gp-jfgx-9qpv | [email protected] | PatchVendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-433 | Unparsed Raw Web Content Delivery | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| hyperterse hyperterse | < 2.2.0 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Mar 19, 2026 | Initial Analysis | [email protected] |
| Mar 12, 2026 | New CVE Received | [email protected] |