Security readout for executives and security teams
Plain-English summary
This flaw affects AWS's HealthLake MCP Server used by AI assistants to interact with HealthLake FHIR datastores. A logged-in user could abuse pagination handling to make the server send AWS temporary security credentials to an external endpoint. The vendor recommends upgrading to version 0.0.14 or later.
Executive priority
Treat this as urgent for any deployed HealthLake MCP Server because the described impact is credential exfiltration. Prioritize finding instances, upgrading, and confirming whether exposed credentials require incident review.
Technical view
The issue is server-side request forgery in pagination URL handling before awslabs.healthlake-mcp-server 0.0.14. The server did not validate that pagination URLs remained on the expected HealthLake endpoint, allowing a crafted next_token to redirect later requests and expose AWS temporary credentials.
Likely exposure
Exposure is likely limited to organizations running awslabs.healthlake-mcp-server before 0.0.14, with authenticated user access and AWS temporary credentials available to the server. Systems not using this MCP server are not indicated as affected by the provided sources.
Exploitation context
The bundle does not identify active exploitation, and KEV is false. The CVSS data indicates network reachability, low attack complexity, low privileges, and user interaction. The main business risk is credential exposure that could enable follow-on access outside the MCP server.
Researcher notes
Evidence supports SSRF through unvalidated pagination URLs in next_token handling. The sources name the fixed version but do not provide exploit details or indicators. Avoid assuming broader AWS HealthLake service exposure beyond the MCP server package.
Mitigation direction
- Upgrade awslabs.healthlake-mcp-server to version 0.0.14 or later.
- Review the AWS security bulletin for any updated vendor guidance.
- Restrict MCP server access to trusted authenticated users until upgraded.
- Review AWS temporary credential exposure if exploitation is suspected.
Validation and detection
- Inventory deployments of awslabs.healthlake-mcp-server.
- Confirm installed versions are 0.0.14 or later.
- Identify whether the server can access AWS temporary credentials.
- Review MCP server and AWS logs for unexpected outbound pagination requests.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-15643 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.2 (4.0)
- Known Exploited
- No
- Published
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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——AMZNCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N2.15.2AMZNVulnerability scoring details
Base CVSS 4.0 score
9.2CriticalVector: 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
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://pypi.org/project/awslabs.healthlake-mcp-server/0.0.14/CVE reference, AMZN · release-notes
- https://aws.amazon.com/security/security-bulletins/2026-054-aws/CVE reference, AMZN · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.