CVE-2026-15643
SSRF in AWS HealthLake MCP server allows exfiltration of AWS temporary credentials.
Is CVE-2026-15643 being exploited?
Not confirmed. CVE-2026-15643 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-15643?
CVE-2026-15643 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-15643?
Yes. A fix has been recorded for CVE-2026-15643. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-15643 affect?
CVE-2026-15643 affects awslabs.healthlake-mcp-server < 0.0.14, AWS HealthLake FHIR datastores using MCP server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-15643?
Upgrade to awslabs.healthlake-mcp-server >= 0.0.14; rotate AWS creds if exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated SSRF via crafted next_token can exfiltrate AWS temporary credentials to attacker-controlled endpoints, enabling data theft and lateral AWS access.
Immediate action required
- affected< 0.0.14
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.