CVE-2026-49120
HighCVSS 8.5Exploitation Probability (EPSS)
Low risk14th percentile - higher than 14% of all known CVEs
Summary
Medplum before version 5.1.14 has an SSRF vulnerability in the subscription worker, allowing authenticated users to perform unauthorized network requests by creating FHIR Subscription resources with arbitrary endpoint URLs. Attackers can point subscriptions at internal addresses like cloud metadata services, databases, or container orchestration endpoints to exfiltrate IAM credentials and patient health records.
Risk Assessment
An attacker can access internal network resources, steal cloud credentials, and exfiltrate sensitive patient medical data.
Recommendation
Update Medplum to version 5.1.14 or later.
Other vulnerabilities in Medplum
See all- CVE-2026-53728High
Medplum prior to version 5.1.6 has a vulnerability in the external identity provider callback at GET /auth/external that accepts attacker-controlled redirect URIs that only need to start with a registered client redirect URI. After a successful external IdP login, the server appends Medplum login and code values to that attacker-supplied URL and issues a redirect. Because the external login request state is serialized as raw JSON and later trusted, an attacker who can tamper with state.redirectUri can cause Medplum to redirect authorization artifacts to an attacker-controlled endpoint, leading to a cross-origin authorization code leak. This issue has been patched in version 5.1.6.
- CVE-2026-44506High
Medplum versions 4.1.10 through 5.1.6 have a vulnerability in the /oauth2/register endpoint that could return the client_secret of preconfigured OAuth clients defined via the defaultOAuthClients server configuration when a matching redirect_uri was provided. This issue has been patched in version 5.1.7.
Original NVD description (English source)
Medplum before 5.1.14 contains a server-side request forgery vulnerability in the subscription worker that allows authenticated users to perform unauthorized internal network requests by creating FHIR Subscription resources with arbitrary endpoint URLs. Attackers can point subscription endpoints at internal addresses such as cloud instance metadata services, internal databases, or container orchestration endpoints to exfiltrate IAM credentials and patient health records via the POST body containing full FHIR resource payloads.