CVE-2026-47661: 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. 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 versions before 2.0.0 have an improper limitation of pathname to a restricted directory (CWE-22) in the /$result endpoint. The endpoint accepts a file parameter that is not normalized or confined to the job-specific directory, allowing path traversal attacks. Since the async export scratch space shares the warehouse database root with persisted resource tables, an attacker can leverage their export job ID to read arbitrary files from the warehouse. This vulnerability has a CVSS 4.0 score of 8.7 (high severity) and does not require privileges or user interaction to exploit. The vulnerability is resolved in version 2.0.0.
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 or other critical information stored alongside the export scratch space. The vulnerability does not require privileges or user interaction, increasing its risk. No known exploits in the wild have been reported.
Mitigation Recommendations
This vulnerability is fixed in Pathling Server 2.0.0. Users should upgrade to version 2.0.0 or later to fully remediate the issue. As an interim mitigation, disable async export operations by setting pathling.operations.exportEnabled, patientExportEnabled, groupExportEnabled, and bulkSubmitEnabled to false, or enable authentication and restrict export capabilities to trusted callers. Patch status is not explicitly confirmed beyond the fixed version 2.0.0; check vendor advisories for updates.
CVE-2026-47661: 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. 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
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Pathling Server versions before 2.0.0 have an improper limitation of pathname to a restricted directory (CWE-22) in the /$result endpoint. The endpoint accepts a file parameter that is not normalized or confined to the job-specific directory, allowing path traversal attacks. Since the async export scratch space shares the warehouse database root with persisted resource tables, an attacker can leverage their export job ID to read arbitrary files from the warehouse. This vulnerability has a CVSS 4.0 score of 8.7 (high severity) and does not require privileges or user interaction to exploit. The vulnerability is resolved in version 2.0.0.
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 or other critical information stored alongside the export scratch space. The vulnerability does not require privileges or user interaction, increasing its risk. No known exploits in the wild have been reported.
Mitigation Recommendations
This vulnerability is fixed in Pathling Server 2.0.0. Users should upgrade to version 2.0.0 or later to fully remediate the issue. As an interim mitigation, disable async export operations by setting pathling.operations.exportEnabled, patientExportEnabled, groupExportEnabled, and bulkSubmitEnabled to false, or enable authentication and restrict export capabilities to trusted callers. Patch status is not explicitly confirmed beyond the fixed version 2.0.0; check vendor advisories for updates.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-19T21:10:38.797Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a772657bf8831d539846b93
Added to database: 08/08/2026, 12:51:35 UTC
Last enriched: 08/15/2026, 15:10:15 UTC
Last updated: 09/22/2026, 01:52:43 UTC
Views: 59
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.