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 bulk-submit operation allows an allowed submitter to supply an explicit oauthMetadataUrl parameter that is not validated against pathling.bulkSubmit.allowableSources. When present, the bulk-submit OAuth flow trusts metadata and the returned token_endpoint from the caller-chosen location, then builds outbound OAuth client authentication directly from the submitter's stored credentials. This is fixed in Pathling Server 2.0.0.
CVE-2026-47660
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
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 computedSeverity87% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 23%
- KEV
- Not listed
Published
August 7, 2026
Last Modified
August 7, 2026
Advisory Details (1)
Auto-updated Aug 7, 2026Explicit oauthMetadataUrl in bulk-submit allows OAuth client credential exfiltration · Advisory · aehrc/pathling · GitHub
https://github.com/aehrc/pathling/security/advisories/GHSA-245h-c573-9vr5Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 43× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 10:21 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 23:43 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 23:30 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 23:18 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 22:56 UTCEG score recompute
- 2026-08-24 10:54 UTCEG score recompute
- 2026-08-23 10:46 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 10:42 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 10:37 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 22:27 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 22:21 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 22:17 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 22:13 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
Show 18 moreShow fewer
- 2026-08-16 10:10 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 10:07 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 09:59 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 21:54 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 21:49 UTCEG score recompute
- 2026-08-11 09:48 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 21:40 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 21:36 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 20:30 UTCEG score recompute
- 2026-08-07 20:12 UTCEG score recompute
- 2026-08-07 20:12 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-47660?
When was CVE-2026-47660 disclosed?
Is CVE-2026-47660 actively exploited?
What is the CVSS score of CVE-2026-47660?
How do I remediate CVE-2026-47660?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-47660
Is Your Infrastructure Affected by CVE-2026-47660?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.