Telnyx MCP Server through 6.83.0 Missing Authentication on Streamable HTTP Transport
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| team-telnyx | telnyx-mcp | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Telnyx | Telnyx-mcp |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.727% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| 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
|