CVE-2026-47660: Pathling: Explicit oauthMetadataUrl in bulk-submit allows OAuth client credential exfiltration
Pathling is a set of tools that make it easier to use FHIR and clinical terminology within health data analytics. Prior to version 2.0.0 of Pathling Server, Pathling's bulk-submit operation allows an allowed submitter to supply an explicit oauthMetadataUrl parameter that is not validated against pathling.bulkSubmit.allowableSources. When present, the bulk-submit OAuth flow trusts metadata and the returned tokenendpoint from the caller-chosen location, then builds outbound OAuth client authentication directly from the submitter's stored credentials. This is fixed in Pathling Server 2.0.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Pathling Serverto a version that resolves this vulnerability.Fixed in 2.0.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-47660?
CVE-2026-47660 has a risk score of 55, indicating a moderate severity level.
How do I fix CVE-2026-47660?
To fix CVE-2026-47660, upgrade to version 2.0.0 or later of Pathling Server where the vulnerability is addressed.
What type of vulnerability is CVE-2026-47660 classified as?
CVE-2026-47660 is classified as a Server-Side Request Forgery (SSRF) vulnerability.
What can be affected by CVE-2026-47660?
CVE-2026-47660 can lead to OAuth client credential exfiltration when the oauthMetadataUrl parameter is not properly validated.
Who is impacted by CVE-2026-47660?
Users of Pathling Server versions prior to 2.0.0 are impacted by CVE-2026-47660.