{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-19202 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-19202 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-19202 is a critical vulnerability in Google mcp-toolbox-sdk-python, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-19202 and fix it if it is affected.\n\nWhat it is: CVE-2026-19202 is a critical vulnerability in Google mcp-toolbox-sdk-python, published on 22 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-19202 in the wild and no public exploit code.\n\nAffected product: Google mcp-toolbox-sdk-python. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-19202/ (Markdown: https://insights.sbomify.com/CVE-2026-19202/index.md)","id":"CVE-2026-19202","markdown":"https://insights.sbomify.com/CVE-2026-19202/index.md","name":"CVE-2026-19202","record":{"aliases":["GHSA-jcjp-gr26-563j"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Python SDK","requires_auth":"none","summary":"Attackers can capture and replay cached Google ID tokens intended for one service against another, leading to impersonation and unauthorized access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-524","name":"Use of Cache Containing Sensitive Information"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Token Cache Reuse in mcp-toolbox-sdk-python","id":"CVE-2026-19202","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"A client may issue specially crafted HTTP/1.1 chunked requests to a Jetty server that cause Jetty and an intermediary proxy to interpret dif","id":"CVE-2026-19203"},"packages":[],"prev":{"headline":"Denial of Service via Unbounded Recursion in go-attestation Windows SIPA Parser","id":"CVE-2026-19201"},"products":["mcp-toolbox-sdk-python"],"published":"2026-09-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-23","vendors":["Google"]},"summary":"Attackers can capture and replay cached Google ID tokens intended for one service against another, leading to impersonation and unauthorized access.","url":"https://insights.sbomify.com/CVE-2026-19202/"}