CVE-2026-47662

Pathling $bulk-submit allows bearer-token exfiltration and persistent warehouse poisoning via unvalidated manifest output URLs

Published Aug 7, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
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 typed CRUD/search/batch FHIR surface allows an authenticated caller with only coarse operation authorities to act on attacker-chosen resource families because those entrypoints do not consistently enforce the documented per-resource `read` and `write` authorities. The documented authorization model requires an operation authority (e.g. `pathling:search`) to be paired with the matching per-resource `read` or `write` authority (e.g. `pathling:read:Patient`). Delete and batch are documented to require write authority for all referenced resource types. However, typed search, update, and related handlers are annotated only with `@OperationAccess(...)` and act on the provider-selected resource type without checking the corresponding per-resource authority. This is fixed in Pathling Server 2.0.0.

Analysis

AI-generated

Technical impact

The vulnerability in Pathling Server allows an authenticated caller with broad operation authorities to act on arbitrary FHIR resource families because the API endpoints do not enforce per-resource read or write permissions. An attacker can use these endpoints to exfiltrate bearer tokens and poison the warehouse by providing unvalidated manifest output URLs, thereby compromising data integrity and exposing protected health information.

Affected Systems

Pathling Server is impacted; all releases prior to version 2.0.0 of Pathling Server have this flaw.

Risk and Exploitability

The CVSS score of 8.7 indicates high severity. The attack requires only authentication with coarse operation authorities and can be carried out via normal API calls, making exploitation straightforward for insiders or compromised accounts. The flaw is not listed in the CISA KEV catalog and the EPSS score is not available, but the high CVSS and lack of additional mitigations suggest a significant risk of exploitation in environments where Pathling is exposed to internal or external users.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Pathling Server to version 2.0.0 or later. This deployment fixes the authorization enforcement flaw.
  • Limit operation authorities to only those explicitly needed for each user, ensuring per-resource read and write permissions are required.
  • Validate and sanitize any manifest output URLs to prevent server‑side request forgery and warehouse poisoning attacks.

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

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Aehrc
Aehrc pathling
Vendors & Products Aehrc
Aehrc pathling
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 typed CRUD/search/batch FHIR surface allows an authenticated caller with only coarse operation authorities to act on attacker-chosen resource families because those entrypoints do not consistently enforce the documented per-resource `read` and `write` authorities. The documented authorization model requires an operation authority (e.g. `pathling:search`) to be paired with the matching per-resource `read` or `write` authority (e.g. `pathling:read:Patient`). Delete and batch are documented to require write authority for all referenced resource types. However, typed search, update, and related handlers are annotated only with `@OperationAccess(...)` and act on the provider-selected resource type without checking the corresponding per-resource authority. This is fixed in Pathling Server 2.0.0.
Title Pathling $bulk-submit allows bearer-token exfiltration and persistent warehouse poisoning via unvalidated manifest output URLs
Weaknesses CWE-20
CWE-522
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'}

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-522

    Insufficiently Protected Credentials

  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 13, 2026, 6:36 PM
Reserved
May 19, 2026, 9:10 PM
Status
Deferred
Published
Aug 7, 2026, 9:17 PM
Modified
Oct 23, 2026, 8:10 PM