CVE-2026-15643 AWS HealthLake MCP Server SSRF via Pagination URL

Critical 9.2 Published Updated

Remote authenticated users can exfiltrate AWS credentials via SSRF in pagination handling, requiring an upgrade to the AWS HealthLake MCP Server.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
None listed

What is CVE-2026-15643?

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.

Official 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.

Its recommended to upgrade to version 0.0.14 or later.

Weakness: CWE-918

Which versions are affected by CVE-2026-15643?

How do I fix CVE-2026-15643?

No fix has been published for CVE-2026-15643 yet. Limit exposure of the affected software until one is available.

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is CVE-2026-15643 being exploited?

There is no known exploitation of CVE-2026-15643 in the wild and no public exploit code.

Sources

Is CVE-2026-15643 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free