/

CVE-2026-81098

Severity:

CRITICAL RISK

(9.1)

Missing Authentication (CWE-306) in Telnyx MCP Server

CVE-2026-81098

Deferred

Vulnerability type

Category:

Missing Authentication

CWE:

CWE-306

Impact:

Unauthorized access and privileged API actions

Severity:

CRITICAL RISK

(9.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

The Telnyx MCP server could expose its HTTP-based MCP transport on every network interface without requiring a caller credential. An unauthenticated caller who could reach the service might dispatch tools that used the server's stored Telnyx API key, client secret, and code-execution key.

Affected context

The vulnerability occurs in deployments of the Telnyx MCP server where the HTTP transport listens on all interfaces and accepts requests without enforcing caller authentication. It is particularly risky when the MCP port is reachable from untrusted networks, because tool dispatch can use credentials held by the server rather than credentials supplied by the caller.

Exploit preconditions

  • Attack surface: The MCP server's HTTP transport and root request path
  • Required access: Network reachability to the exposed MCP listening port; no valid caller credential is required
  • Trigger point: An HTTP request that initializes an MCP session and dispatches a tool
  • Why exploitation is possible: Missing authentication enforcement allows an unauthenticated request to proceed, while tool dispatch forwards server-held credentials to the upstream service

Why this happens

The underlying issue is a missing authentication control, mapped to CWE-306: Missing Authentication for Critical Function. The HTTP listener was reachable beyond the local host, and authentication headers were parsed in a non-failing mode when absent. Because middleware did not require a valid caller credential before initialization and tool dispatch, the server treated unauthenticated requests as authorized and applied its own privileged credentials.

Potential impact

  • An unauthenticated caller could invoke exposed MCP tools
  • Attackers may perform Telnyx API actions using the server's stored credentials
  • Account resources or communications could be modified or abused
  • Client secrets and code-execution capabilities could be misused
  • The service could become a pivot point for broader compromise

General mitigation guidance

Mitigation generally focuses on enforcing authentication before any session initialization or tool dispatch and reducing network exposure.

Common defensive patterns include:

  • Bind administrative or integration transports to loopback or explicitly trusted interfaces by default
  • Require a valid server-side caller credential and fail closed when authentication material is absent or malformed
  • Apply authorization checks to every tool and sensitive operation
  • Avoid forwarding broad server-held credentials when narrower, scoped credentials are sufficient
  • Store credentials securely and grant the MCP process only the privileges it requires
  • Place the service behind network controls that restrict access to approved clients

How teams detect issues like this

Organizations can look for:

  • Static analysis rules that flag network listeners bound to wildcard interfaces without authentication middleware
  • Code review signals such as optional authentication parsing, permissive defaults, and tool dispatch before authorization
  • Integration tests confirming that missing, invalid, and expired credentials are rejected before initialization and tool execution
  • Network telemetry showing unexpected clients connecting to MCP ports
  • Policy enforcement requiring authentication and explicit interface binding for service transports

Automated security review tools may help identify missing authorization checks and unsafe credential forwarding patterns.

Sources

SourceLink
github.comgithub.com/team-telnyx/telnyx-node
github.comgithub.com/team-telnyx/telnyx-node/pull/450
github.comgithub.com/team-telnyx/telnyx-node/security/advisories/GHSA-46jp-xr2h-fw7h
vulncheck.comvulncheck.com/advisories/telnyx-mcp-server-through-6.83.0-missing-authentication-on-streamable-http-transport

Frequently asked

questions

It can be remotely exploitable when the MCP HTTP port is reachable by an untrusted client. Exploitation does not require a valid caller credential in the affected configuration.

The attacker needs network connectivity to the exposed MCP transport. They do not need access to the server's stored Telnyx credentials if the vulnerable request path forwards those credentials during tool dispatch.

Require authentication and authorization before session initialization or tool execution, fail closed when credentials are absent, and limit the listener to trusted interfaces and networks.

Use deny-by-default middleware, test unauthenticated and malformed requests in CI, review wildcard network bindings, and minimize the scope and privileges of credentials used by integration services.

Find out what's already
exploitable in your codebase.