CVE-2026-47660 Pathling: Explicit oauthMetadataUrl in bulk-submit allows OAuth client credential exfiltration
Attackers can exfiltrate OAuth client credentials by supplying a malicious oauthMetadataUrl in bulk-submit operations, bypassing source validation.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-47660?
CVE-2026-47660 is a high-severity server-side request forgery vulnerability in aehrc pathling, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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 `token_endpoint` 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.
Which versions are affected by CVE-2026-47660?
How do I fix CVE-2026-47660?
No fix has been published for CVE-2026-47660 yet. Limit exposure of the affected software until one is available.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-47660 being exploited?
There is no known exploitation of CVE-2026-47660 in the wild and no public exploit code.
Sources
Also known as GHSA-245h-c573-9vr5.