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 `/$result` endpoint allows a caller who can obtain any valid async export job ID to supply `file` parameter values containing path traversal sequences. The handler verifies only the supplied `job` and never normalises or confines the requested `file` path to that job's `jobs/<jobId>` directory before opening it as a filesystem resource. Because async export scratch space lives under the same warehouse database root as persisted resource tables, an attacker can use their own export job to read other files from the warehouse. This is fixed in Pathling Server 2.0.0. The `$result` handler now resolves and canonicalizes the requested file path and rejects any request that escapes the job's `jobs/<jobId>` directory. As an interim mitigation, disable the async export operations (`pathling.operations.exportEnabled`, `patientExportEnabled`, `groupExportEnabled`, `bulkSubmitEnabled`) or enable authentication and restrict export capability to trusted callers.
Published: 2026-08-07
Score: 8.7 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A path traversal vulnerability in Pathling’s /$result endpoint allows an attacker who can obtain a valid asynchronous export job ID to craft a file parameter containing traversal sequences. The handler fails to normalize or confine the requested path to the specific job’s directory, enabling the attacker to read any file located under the warehouse database root. This effectively turns the endpoint into a read‑capable Server‑Side Request Forgery that can expose sensitive internal files and potentially expose persisted FHIR resources. The CVSS score of 8.7 indicates a high severity impact with significant confidentiality risk.

Affected Systems

Pathling Server versions prior to 2.0.0 are affected. The vulnerability exists in the server component of the Pathling tool suite, which facilitates FHIR and clinical terminology analytics. No specific minor version details beyond 2.0.0 are provided, so any deployment using an earlier release should be considered vulnerable until patched.

Risk and Exploitability

The vulnerability’s high CVSS score combined with the lack of an EPSS rating and absence from the CISA KEV catalog suggest that while exploitation is plausible, it may not yet be widely automated. Attackers can exploit the flaw by sending an HTTP request to the /$result endpoint with syntactically crafted path traversal payloads, provided they possess at least one valid export job identifier. An authenticated or privileged attacker inside the network where Pathling is deployed can therefore read arbitrary files, potentially gaining access to sensitive medical data or configuration files. Mitigating through an upgrade or disabling export operations is therefore strongly recommended to reduce risk.

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

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Pathling Server to version 2.0.0 or later, which implements path canonicalization and rejects requests that escape the job’s directory.
  • If an upgrade cannot be performed immediately, disable all async export operations by setting pathling.operations.exportEnabled, patientExportEnabled, groupExportEnabled, and bulkSubmitEnabled to false to stop the vulnerable endpoint from being usable.
  • Alternatively, enable authentication on the system and restrict the import/export API to trusted callers only, effectively preventing unauthorized access to the /$result endpoint.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 07 Aug 2026 20:00:00 +0000

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 `/$result` endpoint allows a caller who can obtain any valid async export job ID to supply `file` parameter values containing path traversal sequences. The handler verifies only the supplied `job` and never normalises or confines the requested `file` path to that job's `jobs/<jobId>` directory before opening it as a filesystem resource. Because async export scratch space lives under the same warehouse database root as persisted resource tables, an attacker can use their own export job to read other files from the warehouse. This is fixed in Pathling Server 2.0.0. The `$result` handler now resolves and canonicalizes the requested file path and rejects any request that escapes the job's `jobs/<jobId>` directory. As an interim mitigation, disable the async export operations (`pathling.operations.exportEnabled`, `patientExportEnabled`, `groupExportEnabled`, `bulkSubmitEnabled`) or enable authentication and restrict export capability to trusted callers.
Title Pathling has path traversal in $import-pnp manifest that enables read-capable SSRF via /jobs/{jobId}/{filename}
Weaknesses CWE-22
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'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-07T19:49:51.968Z

Reserved: 2026-05-19T21:10:38.796Z

Link: CVE-2026-47659

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-07T21:30:18Z

Weaknesses
  • CWE-22

    Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

  • CWE-918

    Server-Side Request Forgery (SSRF)