External risk intelligence

Telnyx MCP Server Missing Authentication on HTTP Transport.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-81098

The vulnerability involves an HTTP server component designed to expose an MCP (Model Context Protocol) service on all network interfaces. Because this service uses standard HTTP transport and is bound to all interfaces by default in the affected configurations, it is commonly exposed as a network-accessible service in deployments.

Missing Authentication

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in the Telnyx MCP server allowed unauthenticated access to sensitive credentials by exposing an HTTP service without requiring caller credentials. This could enable an unauthorized party to gain access to and potentially misuse these credentials. The main concern is confirming relevance and exposure within your environment.

Unauthenticated access to sensitive credentials.
Exposed HTTP service on all interfaces.
Confirm relevance and exposure.

Attack Path

How an attacker could exploit the issue

An attacker could reach the Telnyx MCP server over the network and interact with its HTTP transport without providing any credentials. This unauthenticated access allows an attacker to exploit the server's handling of authentication headers, leading to the dispatch of stored server credentials to an upstream endpoint. By leveraging these credentials, an attacker could potentially execute code or gain further unauthorized access.

Network access to the server port required.
Unauthenticated HTTP request triggers vulnerability.
Compromise of server credentials and code execution.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, an unauthenticated caller able to reach the MCP server's HTTP transport port could impersonate a legitimate user by forwarding the server's own stored credentials to an upstream endpoint. This could lead to unauthorized actions on behalf of the server.

Server credentials and API keys at risk.
Unauthenticated network requests to the port.
Unauthorized actions with server privileges.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners and infrastructure or platform teams are likely responsible for addressing this vulnerability. The first practical step involves identifying all instances of the affected Telnyx MCP server, determining their network reachability and business criticality, and then locating the accountable owner to plan remediation based on risk.

Identify accountable application owners.
Verify network reachability and criticality.
Plan remediation based on identified risk.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is the Telnyx MCP server?

The Telnyx MCP server is a component within the Telnyx Node.js library that implements the Model Context Protocol (MCP). It is used to facilitate communication between AI models and external tools, allowing the server to interact with services by dispatching commands. It relies on internal API keys and secrets to authorize these interactions with upstream endpoints.

What is the vulnerability in CVE-2026-81098?

This vulnerability is classified as CWE-306, which means it involves missing authentication for a critical function. In the affected Telnyx MCP server, the HTTP transport layer fails to verify caller credentials. Because the system does not enforce a check when authentication headers are absent, an unauthorized user can interact with the server as if they were an authorized client.

How can an attacker trigger this vulnerability?

An attacker triggers this by sending an unauthenticated HTTP request directly to the MCP server's network port. The server incorrectly interprets this request as valid and proceeds to dispatch its own stored credentials—including the Telnyx API key and client secret—to an upstream endpoint. Notably, simply using the server for authorized, properly authenticated tasks does not trigger this flaw; it specifically requires the absence of credentials.

Is my instance affected by this CVE-2026-81098 vulnerability?

According to Halo Surface Signal, this vulnerability is highly relevant if your MCP server is bound to all network interfaces, as it defaults to exposing the service globally rather than just to the local machine. You should consider this an external risk if the server port is reachable over your network or the internet, as the design flaw allows any reachable party to bypass authentication checks.

What should I do to address this risk?

Start by auditing your environment to locate all instances of the Telnyx MCP server and determine their network reachability. Once identified, work with the relevant application owners to assess the business criticality of those specific services. Prioritize restricting access to these ports immediately to ensure only authorized local or internal processes can communicate with the server.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.