{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-15643 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-15643 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-15643 is a critical server-side request forgery vulnerability in awslabs.healthlake-mcp-server, published on 14 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-15643 and fix it if it is affected.\n\nWhat it is: CVE-2026-15643 is a critical server-side request forgery vulnerability in awslabs.healthlake-mcp-server, published on 14 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-15643 in the wild and no public exploit code.\n\nAffected product: awslabs.healthlake-mcp-server. 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-15643/ (Markdown: https://insights.sbomify.com/CVE-2026-15643/index.md)","id":"CVE-2026-15643","markdown":"https://insights.sbomify.com/CVE-2026-15643/index.md","name":"CVE-2026-15643","record":{"aliases":[],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"AWS HealthLake MCP Server","requires_auth":"low_privilege","summary":"Remote authenticated users can exfiltrate AWS credentials via SSRF in pagination handling, requiring an upgrade to the AWS HealthLake MCP Server.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[],"cvss":{"score":9.2,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:N/SC:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"AWS HealthLake MCP Server (awslabs.healthlake-mcp-server) is a Model Context Protocol server that enables AI assistants to interact with AWS HealthLake FHIR datastores. A server-side request forgery in the pagination handling component in AWS awslabs.healthlake-mcp-server before 0.0.14 on all platforms might allow a remote authenticated user to exfiltrate AWS temporary security credentials to an arbitrary endpoint via a crafted next_token parameter. The server does not validate that pagination URLs point back to the expected HealthLake endpoint, allowing an actor to redirect subsequent requests to an actor-controlled server.\n\nIts recommended to upgrade to version 0.0.14 or later.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"AWS HealthLake MCP Server SSRF via Pagination URL","id":"CVE-2026-15643","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Powerkit \u003c= 3.1.0 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'style' Shortcode Attribute","id":"CVE-2026-15644"},"packages":[],"prev":{"headline":"Information disclosure in Server","id":"CVE-2026-15642"},"products":["awslabs.healthlake-mcp-server"],"published":"2026-07-14","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["AWS"]},"summary":"Remote authenticated users can exfiltrate AWS credentials via SSRF in pagination handling, requiring an upgrade to the AWS HealthLake MCP Server.","url":"https://insights.sbomify.com/CVE-2026-15643/"}