CVE-2026-47659: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in aehrc pathling
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.
AI Analysis
Technical Summary
Pathling Server before version 2.0.0 has a path traversal vulnerability (CWE-22, CWE-918) in its `/$result` endpoint. The endpoint accepts a `file` parameter that is not normalized or confined to the expected job directory, allowing an attacker with any valid async export job ID to read arbitrary files from the warehouse database root. This occurs because the handler verifies only the job ID but does not restrict the file path to the job's `jobs/<jobId>` directory. The vulnerability is resolved in version 2.0.0 by resolving and canonicalizing the requested file path and rejecting requests that escape the job directory. Interim mitigations include disabling async export features or enforcing authentication and access control on export operations.
Potential Impact
An unauthenticated attacker who can obtain any valid async export job ID can exploit this vulnerability to read arbitrary files from the warehouse database root. This could lead to unauthorized disclosure of sensitive health data and other resources stored alongside the export scratch space. The vulnerability has a high severity with a CVSS 4.0 score of 8.7, indicating network exploitable with no privileges or user interaction required and high impact on confidentiality.
Mitigation Recommendations
A fix is available in Pathling Server version 2.0.0, which properly canonicalizes and restricts file paths to the job directory. Until upgrading, it is recommended to disable async export operations (`pathling.operations.exportEnabled`, `patientExportEnabled`, `groupExportEnabled`, `bulkSubmitEnabled`) or enable authentication and restrict export capabilities to trusted callers to mitigate exploitation risk.
CVE-2026-47659: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in aehrc pathling
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.
CVSS v4.0
Score 8.7high
Affected software
aehrc
pathling
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Pathling Server before version 2.0.0 has a path traversal vulnerability (CWE-22, CWE-918) in its `/$result` endpoint. The endpoint accepts a `file` parameter that is not normalized or confined to the expected job directory, allowing an attacker with any valid async export job ID to read arbitrary files from the warehouse database root. This occurs because the handler verifies only the job ID but does not restrict the file path to the job's `jobs/<jobId>` directory. The vulnerability is resolved in version 2.0.0 by resolving and canonicalizing the requested file path and rejecting requests that escape the job directory. Interim mitigations include disabling async export features or enforcing authentication and access control on export operations.
Potential Impact
An unauthenticated attacker who can obtain any valid async export job ID can exploit this vulnerability to read arbitrary files from the warehouse database root. This could lead to unauthorized disclosure of sensitive health data and other resources stored alongside the export scratch space. The vulnerability has a high severity with a CVSS 4.0 score of 8.7, indicating network exploitable with no privileges or user interaction required and high impact on confidentiality.
Mitigation Recommendations
A fix is available in Pathling Server version 2.0.0, which properly canonicalizes and restricts file paths to the job directory. Until upgrading, it is recommended to disable async export operations (`pathling.operations.exportEnabled`, `patientExportEnabled`, `groupExportEnabled`, `bulkSubmitEnabled`) or enable authentication and restrict export capabilities to trusted callers to mitigate exploitation risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-19T21:10:38.796Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a76387dbf8831d53911445c
Added to database: 08/07/2026, 19:56:45 UTC
Last enriched: 08/15/2026, 15:33:41 UTC
Last updated: 09/21/2026, 22:01:35 UTC
Views: 58
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.