CVE-2026-81098

Telnyx MCP Server before 7.11.0 Missing Authentication on Streamable HTTP Transport

Published Aug 27, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
The Telnyx MCP server exposed its HTTP transport on every interface and did not require a caller credential. packages/mcp-server/src/http.ts served MCP on the root path with a listener bound to all interfaces and parsed the caller's authentication headers in a mode that did not fail when they were absent, so a request without any credential completed initialisation and dispatched tools. Dispatch forwarded the server's own stored credentials, the Telnyx API key and client secret together with the code-execution key, to the upstream endpoint, so an unauthenticated caller able to reach the port acted with them. The current code defaults the host to loopback, requires a server API key, and enforces it in middleware.

Analysis

AI-generated

Technical impact

The Telnyx MCP Server exposes its HTTP transport on all network interfaces and does not enforce caller authentication when processing requests. A request without any credential is accepted, the server completes initialization, dispatches tools, and forwards the server’s own stored credentials—including the Telnyx API key, client secret, and a code‑execution key—to the upstream endpoint. Consequently, an unauthenticated attacker who can reach the exposed port can execute code or otherwise manipulate the upstream system with privileged credentials, resulting in a severe breach of confidentiality and integrity.

Affected Systems

Telnyx MCP Server is affected by this vulnerability in all releases up to and including version 6.83.0. The issue arises from the HTTP listener being bound to all interfaces and the authentication logic allowing empty headers. Users running any version of Telnyx MCP Server within that range are therefore vulnerable.

Risk and Exploitability

The CVSS score of 9.3 categorizes this flaw as critical, and while EPSS is not available, the lack of authentication on a widely exposed service indicates a likely exploitation vector from external networks. The vulnerability is not listed in the CISA KEV catalog, but the exposure of privileged credentials to an unauthenticated caller elevates its impact dramatically. Attackers could remotely send HTTP requests to the MCP Server’s root path, acquire the embedded credentials, and use them to subvert the upstream endpoint. The high severity and ease of exploitation underscore the need for immediate remediation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Telnyx MCP Server to a version where the default host is loopback and authentication is enforced in middleware (any release following 6.83.0).
  • If an upgrade cannot be performed immediately, restrict network exposure by configuring the server to bind only to localhost or by applying firewall rules that permit traffic strictly from trusted IP addresses.
  • Disable or remove the feature that forwards stored credentials to the upstream endpoint to prevent credential leakage, and rotate all impacted API keys and secrets after patching or limiting exposure.

Generated by OpenCVE AI on August 27, 2026 at 18:15 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Title Telnyx MCP Server through 6.83.0 Missing Authentication on Streamable HTTP Transport Telnyx MCP Server before 7.11.0 Missing Authentication on Streamable HTTP Transport
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Telnyx
Telnyx telnyx-mcp
Vendors & Products Telnyx
Telnyx telnyx-mcp
Type Values Removed Values Added
Description The Telnyx MCP server exposed its HTTP transport on every interface and did not require a caller credential. packages/mcp-server/src/http.ts served MCP on the root path with a listener bound to all interfaces and parsed the caller's authentication headers in a mode that did not fail when they were absent, so a request without any credential completed initialisation and dispatched tools. Dispatch forwarded the server's own stored credentials, the Telnyx API key and client secret together with the code-execution key, to the upstream endpoint, so an unauthenticated caller able to reach the port acted with them. The current code defaults the host to loopback, requires a server API key, and enforces it in middleware.
Title Telnyx MCP Server through 6.83.0 Missing Authentication on Streamable HTTP Transport
Weaknesses CWE-306
References
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}

cvssV4_0

{'score': 9.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-306

    Missing Authentication for Critical Function

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 20, 2026, 2:31 PM
Reserved
Aug 26, 2026, 4:00 PM
Status
Deferred
Published
Aug 27, 2026, 5:20 PM
Modified
Nov 20, 2026, 3:17 PM