Back to CVE records
Critical 9.1Published Sep 22, 2026

CVE-2026-19202Token Cache Reuse in mcp-toolbox-sdk-python

Updated under an hour ago ()

Does this affect you?

It affects Google mcp-toolbox-sdk-python. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

A caching flaw in the toolbox-core package of the mcp-toolbox-sdk-python SDK causes the same Google ID token to be cached and reused across different audiences. If an application uses the SDK to authenticate to two or more different audiences within the same process, the module-level token cache fails to key its cached tokens by the requested audience. Consequently, a valid, unexpired token minted for a sensitive service (Service A) can be retrieved from the cache and sent to a secondary service (Service B). An attacker who operates, compromises, or monitors traffic to Service B can capture this token and replay it to impersonate the victim application against Service A.

CVSS
9.1 CRITICAL (v4.0, CNA)CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Weakness (CWE)
CWE-524
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Google
NVD analysis
Awaiting Analysis
Record last updated
Sep 23, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Google mcp-toolbox-sdk-python
google:mcp_toolbox_sdk_python (from the name)
through 1.1.0
CNA record

References

  • patch

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.