CVE-2026-47663

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
70(Attend)
EG Risk 70/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity87% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 7, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Typed CRUD/search/batch providers can lead to server-wide PHI exfiltration and cross-resource mutation · Advisory · aehrc/pathling · GitHub

https://github.com/aehrc/pathling/security/advisories/GHSA-q62q-2m46-r7rv

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 10:21 UTCEG score recompute
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-28 00:54 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-27 00:38 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-26 00:25 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 00:26 UTCEG score recompute
  11. 2026-08-24 12:29 UTCEG score recompute
  12. 2026-08-23 00:32 UTCEG score recompute
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-22 00:38 UTCEG score recompute
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 00:45 UTCEG score recompute
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 00:49 UTCEG score recompute
  19. 2026-08-19 17:04 UTCEPSS rescore
  20. 2026-08-19 00:51 UTCEG score recompute
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-18 00:56 UTCEG score recompute
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-17 00:37 UTCEG score recompute
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 20 more
  1. 2026-08-16 12:40 UTCEG score recompute
  2. 2026-08-16 02:14 UTCEPSS rescore
  3. 2026-08-15 12:47 UTCEG score recompute
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 00:57 UTCEG score recompute
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 01:03 UTCEG score recompute
  8. 2026-08-12 13:51 UTCEPSS rescore
  9. 2026-08-12 01:10 UTCEG score recompute
  10. 2026-08-11 01:17 UTCEG score recompute
  11. 2026-08-11 00:00 UTCEPSS rescore
  12. 2026-08-10 13:20 UTCEG score recompute
  13. 2026-08-10 13:01 UTCEG score recompute
  14. 2026-08-09 21:17 UTCEG score recompute
  15. 2026-08-09 13:46 UTCEPSS rescore
  16. 2026-08-08 21:25 UTCEG score recompute
  17. 2026-08-08 16:37 UTCEPSS rescore
  18. 2026-08-07 21:32 UTCEG score recompute
  19. 2026-08-07 20:47 UTCEG score recompute
  20. 2026-08-07 20:47 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-47663?
CVE-2026-47663 is a high vulnerability published on August 7, 2026. 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…
When was CVE-2026-47663 disclosed?
CVE-2026-47663 was first published in the National Vulnerability Database on August 7, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47663 actively exploited?
CVE-2026-47663 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.1% of all scored CVEs.
What is the CVSS score of CVE-2026-47663?
CVE-2026-47663 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-47663?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47663, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-47663

Explore →

Is Your Infrastructure Affected by CVE-2026-47663?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs