CVE-2026-81098

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-27. A secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
52nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 27, 2026

Last Modified

September 24, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
Patch available. Sources: github_pr.
Web page

Telnyx MCP Server through 6.83.0 Missing Authentication on Streamable HTTP Transport | Advisories | VulnCheck

https://www.vulncheck.com/advisories/telnyx-mcp-server-through-6.83.0-missing-authentication-on-streamable-http-transport
GitHub pull request Patch Available

fix: restore MCP server source files from v6.83.0

Patch available: team-telnyx/telnyx-node v7.2.0 (PR #450 merged 2026-06-24)

https://github.com/team-telnyx/telnyx-node/pull/450
Web page

GitHub - team-telnyx/telnyx-node: Node SDK for the Telnyx API · GitHub

https://github.com/team-telnyx/telnyx-node

Vendor Advisories for CVE-2026-81098(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 201× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 351 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 251 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 01:36 UTCEG score recompute
  2. 2026-10-14 01:36 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  4. 2026-10-12 21:46 UTCEG score recompute
  5. 2026-10-12 21:46 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-10-12 14:57 UTCEG score recompute
  8. 2026-10-12 05:22 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  9. 2026-10-11 19:20 UTCEG score recompute
  10. 2026-10-11 16:37 UTCEG score recompute
  11. 2026-10-11 13:55 UTCEG score recompute
  12. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  13. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-10-10 13:47 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  15. 2026-10-10 09:48 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  16. 2026-10-10 05:47 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  17. 2026-10-10 01:56 UTCEG score recompute
  18. 2026-10-10 01:55 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  19. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  20. 2026-10-09 07:16 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-10-09 03:07 UTCEG score recompute
  22. 2026-10-09 03:07 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  23. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-10-08 08:38 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  25. 2026-10-08 04:59 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
Show 75 more
  1. 2026-10-08 01:20 UTCEG score recompute
  2. 2026-10-08 01:20 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  4. 2026-10-07 09:53 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  5. 2026-10-07 05:50 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-10-07 02:11 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  7. 2026-10-06 22:20 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-10-06 18:37 UTCEG score recompute
  9. 2026-10-06 18:37 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  10. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-10-06 14:59 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-10-06 11:11 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-10-06 07:33 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  14. 2026-10-06 00:54 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  15. 2026-10-05 20:31 UTCEG score recompute
  16. 2026-10-05 20:31 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-10-05 16:52 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  19. 2026-10-05 11:19 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  20. 2026-10-05 07:22 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-10-05 03:43 UTCEG score recompute
  22. 2026-10-05 03:43 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  23. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-10-04 23:20 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  25. 2026-10-04 19:39 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  26. 2026-10-04 15:58 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  27. 2026-10-04 12:12 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  28. 2026-10-04 08:34 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  29. 2026-10-04 04:55 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  30. 2026-10-04 01:16 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  31. 2026-10-03 19:21 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  32. 2026-10-03 15:13 UTCEG score recompute
  33. 2026-10-03 15:13 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  34. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  35. 2026-10-03 04:51 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  36. 2026-10-03 01:10 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  37. 2026-10-02 21:31 UTCEG score recompute
  38. 2026-10-02 21:31 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  39. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  40. 2026-10-02 17:42 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  41. 2026-10-02 14:02 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  42. 2026-10-02 09:57 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  43. 2026-10-02 06:19 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  44. 2026-10-02 01:14 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  45. 2026-10-01 19:53 UTCEG score recompute
  46. 2026-10-01 19:53 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  47. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  48. 2026-10-01 12:48 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  49. 2026-10-01 09:09 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  50. 2026-10-01 05:31 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  51. 2026-10-01 01:00 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  52. 2026-09-30 19:55 UTCEG score recompute
  53. 2026-09-30 19:55 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  54. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  55. 2026-09-30 12:20 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  56. 2026-09-30 08:42 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  57. 2026-09-30 05:03 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  58. 2026-09-29 16:09 UTCEG score recompute
  59. 2026-09-29 16:09 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  60. 2026-09-29 12:16 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  61. 2026-09-29 08:37 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  62. 2026-09-29 04:59 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  63. 2026-09-29 01:19 UTCEG score recompute
  64. 2026-09-29 01:19 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  65. 2026-09-28 21:16 UTCEG score recompute
  66. 2026-09-28 21:16 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  67. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  68. 2026-09-28 13:32 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  69. 2026-09-28 09:54 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  70. 2026-09-28 06:15 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  71. 2026-09-28 02:37 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  72. 2026-09-27 22:57 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  73. 2026-09-27 19:18 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1
  74. 2026-09-27 15:38 UTCEG score recompute
  75. 2026-09-27 15:38 UTCGHSA enrichmentGHSA-j929-p4w2-gfw7 · GitHub severity CRITICAL · GitHub CVSS 9.1

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81098?
CVE-2026-81098 is a critical-severity vulnerability; its CVE record was published on August 27, 2026. 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…
When was CVE-2026-81098 made public?
CVE-2026-81098 was made public on August 26, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 27, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-81098 actively exploited?
CVE-2026-81098 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81098?
CVE-2026-81098 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-81098?
A fix for CVE-2026-81098 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-81098 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-81098

Explore →

Is Your Infrastructure Affected by CVE-2026-81098?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs