CVE-2026-15643 - AWS HealthLake MCP Server SSRF via Unvalidated Pagination URL
Bulletin ID: 2026-054-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 07/14/2026 13:00 PM PDT 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. We identified CVE-2026-15643, 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. Impacted versions: < 0.0.14 Please refer to the article below for the most up-to-date and complete information related to this AWS Security Bulletin.
AI Analysis
Technical Summary
AWS HealthLake MCP Server (awslabs.healthlake-mcp-server) before version 0.0.14 contains an SSRF vulnerability in its pagination handling component. The server fails to validate that pagination URLs (via the next_token parameter) point back to the expected HealthLake endpoint, enabling a remote authenticated user to redirect requests to an arbitrary endpoint controlled by an attacker. This flaw could allow exfiltration of AWS temporary security credentials. The vulnerability affects all platforms running versions earlier than 0.0.14. AWS has released version 0.0.14 to address this issue.
Potential Impact
A remote authenticated user can exploit the SSRF vulnerability to redirect pagination requests to attacker-controlled endpoints, potentially exfiltrating AWS temporary security credentials. These credentials retain their full granted authority, which could lead to unauthorized access or actions within the AWS environment. The impact is significant due to the potential compromise of temporary credentials, but exploitation requires authentication.
Mitigation Recommendations
AWS has released version 0.0.14 of awslabs.healthlake-mcp-server to fix this vulnerability. It is recommended to upgrade to this version or later. In the interim, operators should scope IAM policies to least privilege rather than using Resource: "*". The --readonly flag should not be relied upon as a security boundary. Additionally, if an affected version was used, rotating the credentials of the affected role is advised. These steps reduce the risk until the patch is applied.
CVE-2026-15643 - AWS HealthLake MCP Server SSRF via Unvalidated Pagination URL
Description
Bulletin ID: 2026-054-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 07/14/2026 13:00 PM PDT 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. We identified CVE-2026-15643, 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. Impacted versions: < 0.0.14 Please refer to the article below for the most up-to-date and complete information related to this AWS Security Bulletin.
Affected software
pkg:github/aws/healthlake-mcp-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
AWS HealthLake MCP Server (awslabs.healthlake-mcp-server) before version 0.0.14 contains an SSRF vulnerability in its pagination handling component. The server fails to validate that pagination URLs (via the next_token parameter) point back to the expected HealthLake endpoint, enabling a remote authenticated user to redirect requests to an arbitrary endpoint controlled by an attacker. This flaw could allow exfiltration of AWS temporary security credentials. The vulnerability affects all platforms running versions earlier than 0.0.14. AWS has released version 0.0.14 to address this issue.
Potential Impact
A remote authenticated user can exploit the SSRF vulnerability to redirect pagination requests to attacker-controlled endpoints, potentially exfiltrating AWS temporary security credentials. These credentials retain their full granted authority, which could lead to unauthorized access or actions within the AWS environment. The impact is significant due to the potential compromise of temporary credentials, but exploitation requires authentication.
Mitigation Recommendations
AWS has released version 0.0.14 of awslabs.healthlake-mcp-server to fix this vulnerability. It is recommended to upgrade to this version or later. In the interim, operators should scope IAM policies to least privilege rather than using Resource: "*". The --readonly flag should not be relied upon as a security boundary. Additionally, if an affected version was used, rotating the credentials of the affected role is advised. These steps reduce the risk until the patch is applied.
Technical Details
- Article Source
- {"url":"https://aws.amazon.com/security/security-bulletins/rss/2026-054-aws/","fetched":true,"fetchedAt":"2026-07-14T20:15:07.962Z","wordCount":259}
- Classification
- {"confidence":0.94,"severitySource":"heuristic","classifier":"rss-v2"}
Threat ID: 6a5698cb68715ace4322181a
Added to database: 07/14/2026, 20:15:07 UTC
Last enriched: 08/08/2026, 17:30:04 UTC
Last updated: 08/28/2026, 22:52:08 UTC
Views: 158
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.