CVE-2026-47660

Pathling: Explicit oauthMetadataUrl in bulk-submit allows OAuth client credential exfiltration

Published Aug 7, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Pathling Server in versions prior to 2.0.0 accepts an explicit oauthMetadataUrl in its bulk‑submit API without validating it against the allowed source list. The server trusts the supplied metadata, retrieves the token_endpoint from the attacker‑controlled endpoint, and builds a client‑authentication request using the submitter’s stored OAuth credentials. This flaw allows an attacker to exfiltrate those credentials or use them to obtain access tokens for downstream services. The resulting compromise threatens the confidentiality of OAuth client secrets and the resources they protect.

Affected Systems

The vulnerability applies to Pathling Server implementations deployed by Aehrc that are running any version earlier than 2.0.0. Any system that makes bulk‑submit requests to such a server and has an allowed submitter role is at risk.

Risk and Exploitability

With a CVSS score of 8.7 the flaw is considered high severity. The EPSS score is not available, but the attack path requires an authorized submitter to supply a malicious oauthMetadataUrl, which is a remote vector via the bulk‑submit API. Because the server blindly trusts the returned token_endpoint, exploitation can occur without additional privileges. The vulnerability is not reported in the CISA KEV catalog, indicating no known widespread exploitation, yet the potential impact justifies proactive mitigation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Pathling Server to version 2.0.0 or later, where the issue is fixed.
  • If an upgrade is not immediately possible, reconfigure bulk‑submit to reject any explicit oauthMetadataUrl value or restrict allowableSources to trusted and validated URLs only.
  • Monitor bulk‑submit traffic for unauthorized or unexpected token_endpoint requests and audit stored OAuth credentials for signs of compromise.

Generated by OpenCVE AI on August 7, 2026 at 21:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Aehrc
Aehrc pathling
Vendors & Products Aehrc
Aehrc pathling
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Pathling: Explicit oauthMetadataUrl in bulk-submit allows OAuth client credential exfiltration
Weaknesses CWE-522
CWE-918
References
Metrics cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-522

    Insufficiently Protected Credentials

  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 7, 2026, 9:01 PM
Reserved
May 19, 2026, 9:10 PM
Status
Deferred
Published
Aug 7, 2026, 8:16 PM
Modified
Oct 23, 2026, 8:10 PM