Pathling Server versions before 2.0.0 contain an improper input validation vulnerability in the $import-pnp operation. This operation accepts a caller-supplied exportUrl used as a remote FHIR Bulk Export endpoint without restricting it to trusted sources. When PNP credentials are configured, Pathling creates a credentialed bulk-export client targeting the caller-chosen host, downloads manifest-selected files, and reclassifies them as trusted local file:// imports. This process bypasses the allowableSources allowlist that normally protects the $import operation, potentially allowing unauthorized import of data from arbitrary remote endpoints. The vulnerability is addressed in Pathling Server 2.0.0. Workarounds include disabling the $import-pnp operation or not configuring PNP credentials.

An attacker able to invoke the $import-pnp operation can specify an arbitrary exportUrl, causing Pathling Server to download and trust data from an untrusted remote FHIR Bulk Export endpoint. This bypasses the configured allowableSources protection, potentially leading to unauthorized data import and trust boundary violations within health data analytics workflows. The CVSS 4.0 score of 8.6 reflects high impact due to network attack vector, low attack complexity, no privileges required, no user interaction, and high impact on confidentiality and integrity.

A fix is available in Pathling Server version 2.0.0. Until upgrading, users should disable the $import-pnp operation by setting pathling.operations.importPnpEnabled=false or avoid configuring PNP credentials to prevent exploitation of this vulnerability.