dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-15643

HIGH · 7.3 CVSS v3.1 Published 2026-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A server-side request forgery (SSRF) vulnerability in the pagination handling component of AWS HealthLake MCP Server allows authenticated users to supply a crafted next_token parameter that redirects subsequent requests to arbitrary attacker-controlled endpoints. Since the server doesn't validate that pagination URLs point back to the expected HealthLake endpoint, attackers can exfiltrate AWS temporary security credentials to external servers.

MitigationUpgrade to version 0.0.14 or later, which includes proper validation of pagination URLs to ensure they resolve only to the expected HealthLake service endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify AWS HealthLake MCP Server installation
    Locate the AWS HealthLake MCP Server package in your environment. Check for files named 'aws-healthlake-mcp-server', 'healthlake-mcp', or similar, or check installed npm/python packages if using package managers.
    Affected if The server is present in your environment and handles pagination requests.
  2. Determine installed server version
    Run 'npm list aws-healthlake-mcp-server' or 'pip show aws-healthlake-mcp-server' depending on your package manager, or check the package.json/requirements.txt for the version number.
    Affected if The installed version is earlier than 0.0.14 (e.g., 0.0.13, 0.0.12, etc.).
  3. Verify pagination feature is enabled
    Review server configuration files and logs to determine if the pagination feature is actively used. Check if API endpoints supporting pagination (e.g., list_datastore_fhir_datastore, list_fhir_export_jobs) are being called by clients.
    Affected if Pagination is enabled and clients can supply the next_token parameter to paginated endpoints.
  4. Inspect network connectivity
    Review server outbound network access and proxy configurations. Check if the server can make outbound HTTP/HTTPS requests to arbitrary URLs.
    Affected if The server has unrestricted outbound network access that could be leveraged for SSRF redirection.

You are affected if AWS HealthLake MCP Server version is before 0.0.14 and the pagination feature is exposed to authenticated users who can supply custom next_token values.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 0.0.14 or later, which includes proper validation of pagination URLs to ensure they resolve only to the expected HealthLake service endpoint.

Recommended fix High confidence

0.0.14 or later

  1. Check the currently installed version by running: pip show awslabs.healthlake-mcp-server or pip list | grep healthlake-mcp-server
  2. Upgrade to version 0.0.14 or later using: pip install --upgrade awslabs.healthlake-mcp-server>=0.0.14
  3. Verify the upgrade was successful by running: pip show awslabs.healthlake-mcp-server and confirming the version number is 0.0.14 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15643 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15643 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data