CVE-2026-81098

Telnyx MCP HTTP callers could use server-held credentials

team-telnyx · Telnyx MCP server · streamable HTTP

First documented disclosure · Review checkpoint

Summary

An unauthenticated network caller could invoke tools using the server’s upstream credentials.

Severity and exploitation evidence

Critical · 9.3/10 · CVSS 4.0. Severity source.

Exploitation not established: Reviewed public sources describe the weakness, a correction or a controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The all-interface HTTP listener accepted missing authentication and forwarded stored credentials during dispatch.

Conditions required

Network reachability to an affected HTTP listener.

Potential impact

Actions with the server’s Telnyx and code-execution credentials.

Affected versions and configurations

Before 7.11.0 according to current CNA.

Fix and mitigation status

7.11.0 per current CNA; the reviewed v7.11.0 tag enforces the MCP server API key and defaults the listener host to loopback.

Practical next steps

Upgrade, require the MCP server API key and verify the bind address.

Operating lesson

Authenticate callers before using shared upstream credentials.

Evidence and limits

Historical backfill. The GHSA page returns 404; VulnCheck original and maintainer PR remain public. No downstream victim compromise is established. CNA publication is 2026-08-27; this is distinct from the earliest reviewed public source and correction dates. VulnCheck assessments: CVSS 4.0 9.3; CVSS 3.1 9.1. The linked PR #450 restores source files and is not the authentication fix. Direct review of v7.11.0 http.ts and auth.ts confirms fail-closed API-key middleware; the tag’s release was published July 25. Reviewed original VulnCheck advisory publication remains August 27, after the CNA-stated public date. Independent review correction: CNA datePublic is 2026-08-26; the original advisory was published 2026-08-27. Use the earlier authority-stated public date while retaining the date distinction.

Sources