Which versions of Pathling Server are affected by CVE-2026-47664?

Pathling Server versions prior to 2.0.0 contain a permission bypass vulnerability that allows callers to forward configured credentials to attacker-controlled systems and inject unauthorized data.. A patch is available.

How to fix or mitigate CVE-2026-47664?

Within 24 hours: identify all Pathling Server deployments and determine which have PNP credentials configured-these require immediate attention. Within 7 days: upgrade all affected instances to Pathling Server version 2.0.0 or later, prioritizing production systems. Within 30 days: confirm upgrade completion, rotate PNP credentials used during the vulnerable period, and audit API logs for unauthorized $import-pnp operations.

Pathling Server CVE-2026-47664

Q: What is the CVSS score of CVE-2026-47664?

CVE-2026-47664 has a CVSS 4.0 base score of 8.6 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.1%.

EUVD-2026-54651 HIGH

Improper Input Validation (CWE-20)

2026-08-07 GitHub_M

Authentication Bypass Pathling Aehrc

8.6

CVSS 4.0 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

8.6 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

8.1 HIGH

Network-reachable API requires low-privilege access (PR:L); PNP credential theft drives C:H; allowlist bypass enabling arbitrary data import drives I:H; no availability impact described.

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

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Aug 07, 2026 - 21:16 vuln.today

Patch available

Aug 07, 2026 - 21:02 EUVD

CVE Published

Aug 07, 2026 - 20:28 cve.org

HIGH 8.6

DescriptionCVE.org

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, the $import-pnp operation in Pathling Server accepts a caller-supplied exportUrl and uses it as the remote FHIR Bulk Export endpoint without constraining it to a trusted source. When PNP credentials are configured, Pathling builds a credentialed bulk-export client targeting the caller-chosen host, downloads manifest-selected files, and then reclassifies those staged files as trusted local file:// imports - bypassing the configured allowableSources allowlist that protects the ordinary $import operation. This is fixed in Pathling Server 2.0.0. As a workaround, disable the $import-pnp operation (pathling.operations.importPnpEnabled=false) or do not configure PNP credentials.

AnalysisAI

The $import-pnp operation in Pathling Server allows low-privileged callers to supply an arbitrary exportUrl, causing the server to forward its configured PNP credentials to an attacker-controlled FHIR endpoint and stage the returned files as trusted local sources - effectively bypassing the allowableSources allowlist that guards the standard $import operation. All Pathling Server deployments prior to version 2.0.0 with PNP credentials configured are affected, with high confidentiality and integrity impact (credential theft and unauthorized data import). No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, though the attack requires only low-privilege API access and is low-complexity.

Technical ContextAI

Pathling is an open-source health data analytics toolkit built around HL7 FHIR (Fast Healthcare Interoperability Resources), used to perform clinical terminology queries and bulk data operations against FHIR servers. The $import-pnp operation is a FHIR extended operation designed to consume Bulk Export data using PNP (Push Notification Protocol) credentials for authenticated inter-system transfers. The root cause is CWE-20 (Improper Input Validation): the operation accepts a caller-supplied exportUrl without validating it against any trusted-source allowlist, a control that exists for the ordinary $import operation. When PNP credentials are configured, Pathling constructs a credentialed HTTP client targeting the attacker-supplied URL, downloads manifest-specified files from that host, and then reclassifies those staged downloads as trusted local file:// URIs - bypassing the allowableSources security boundary entirely. The affected CPE is cpe:2.3:a:aehrc:pathling:*:*:*:*:*:*:*:* covering all versions before 2.0.0.

RemediationAI

Upgrade Pathling Server to version 2.0.0, which resolves the vulnerability by enforcing trusted-source validation on the exportUrl parameter of the $import-pnp operation. If an immediate upgrade is not feasible, two workarounds are available per the vendor advisory: disable the $import-pnp operation by setting pathling.operations.importPnpEnabled=false (eliminates the attack surface entirely but removes all PNP bulk import capability), or remove PNP credential configuration from the deployment (prevents the credentialed client from being constructed, though this disables PNP-authenticated workflows). The workaround of removing credentials is less robust because it depends on operational discipline rather than a code-level control. The vendor advisory and patch details are at https://github.com/aehrc/pathling/security/advisories/GHSA-69wc-hrxh-5528.