CVE-2026-11717

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.3
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An authentication bypass vulnerability exists in the generic opaque token validation path (validateOpaqueToken) of googleapis/mcp-toolbox.

When verifying an unparsed opaque token via an OAuth 2.0 introspection endpoint (RFC 7662), the toolbox decodes the response into an introspectResp struct where the Active field is declared as a pointer to a boolean (*bool). The code only explicitly rejects a token if the response contains a populated active field set to false (if introspectResp.Active != nil && !*introspectResp.Active). If an introspection endpoint responds with a payload that completely omits the mandatory active key, the internal variable remains nil, causing the conditional check to short-circuit. As a result, Toolbox accepts authorization tokens missing the "active" field, granting access to protected tools and underlying data sources.

CVSS v3
9.3
EG Score
9.3(medium)
EPSS
9.4%
KEV
Not listed

Published

June 18, 2026

Last Modified

June 22, 2026

Advisory Details (1)

Auto-updated Jun 22, 2026
Patch available. Sources: github_pr.
github_pr Patch Available

fix(auth): separate Google and Generic MCP OAuth verification

Patch available: googleapis/mcp-toolbox v1.4.0 (PR #3341 merged 2026-06-04)

https://github.com/googleapis/mcp-toolbox/pull/3341

Vendor Advisories for CVE-2026-11717(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/googleapis/mcp-toolbox1.4.0

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 53× in last 7d / 119× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 119 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-11717?
CVE-2026-11717 is a critical vulnerability published on June 18, 2026. An authentication bypass vulnerability exists in the generic opaque token validation path (validateOpaqueToken) of googleapis/mcp-toolbox. When verifying an unparsed opaque token via an OAuth 2.0 introspection endpoint (RFC 7662), the toolbox decodes the response into an introspectResp struct where…
When was CVE-2026-11717 disclosed?
CVE-2026-11717 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11717 actively exploited?
CVE-2026-11717 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-11717?
CVE-2026-11717 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-11717?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11717, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-11717

Explore →

Is Your Infrastructure Affected by CVE-2026-11717?

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