# CVE-2026-47663: Pathling: Typed CRUD/search/batch providers can lead to server-wide PHI exfiltration and cross-resource mutation

> Authenticated users can bypass per-resource authorization checks to exfiltrate PHI or modify data across resource families in Pathling Server.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-q62q-2m46-r7rv

## What is CVE-2026-47663?

CVE-2026-47663 is a high-severity missing authorization vulnerability in aehrc pathling, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-285 (Improper Authorization)

## Which versions are affected by CVE-2026-47663?


## How do I fix CVE-2026-47663?

No fix has been published for CVE-2026-47663 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-47663 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47663 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47663 and fix it if it is affected.

What it is: CVE-2026-47663 is a high-severity missing authorization vulnerability in aehrc pathling, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47663 exists.

Affected product: aehrc pathling. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47663/ (Markdown: https://insights.sbomify.com/CVE-2026-47663/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47663
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47663
- OSV: https://osv.dev/vulnerability/CVE-2026-47663

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47663/
Summaries are generated and may contain mistakes; the official description above is the record.