CVE-2026-55470

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 50% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. Prior to 6.9.10, the fix for CVE-2026-45367 incompletely patched the DSTU2 module, leaving FHIRPathEngine.matches() in org.hl7.fhir.dstu2/utils/FHIRPathEngine.java to call raw String.matches(sw) without RegexTimeout protection while replaceMatches() was updated, allowing an unauthenticated attacker to trigger catastrophic regex backtracking and exhaust server CPU. This issue is fixed in version 6.9.10.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

Published

June 17, 2026

Last Modified

July 16, 2026

Advisory Details (3)

Auto-updated Jul 8, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
githubMentions a patch (unverified)🟡 PoC Available

Incomplete fix for CVE-2026-45367: DSTU2 FHIRPathEngine.matches() missing RegexTimeout protection allows ReDoS · Advisory · hapifhir/org.hl7.fhir.core · GitHub

https://github.com/hapifhir/org.hl7.fhir.core/security/advisories/GHSA-fxj4-p9xp-37v5
github_release Patch Available

6.9.10

Patch available: hapifhir/org.hl7.fhir.core 6.9.10

https://github.com/hapifhir/org.hl7.fhir.core/releases/tag/6.9.10
github_commit Patch Available

commit 56376f798622 (hapifhir/org.hl7.fhir.core)

Patch available: hapifhir/org.hl7.fhir.core 6.9.10 (contains commit 56376f798622)

https://github.com/hapifhir/org.hl7.fhir.core/commit/56376f7986222626af061ca7fc27ee1ab030e590

Vendor Advisories for CVE-2026-55470(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatorg.hl7.fhir.dstu22026-08-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 1 ecosystem)
Maven(4)
PackageVulnerable rangeFix by version rangeDependents
ca.uhn.hapi.fhir:org.hl7.fhir.convertors0.0.1 ... 6.9.9 (391 versions)
  • every version up to 6.9.10: fixed in 6.9.10
—
ca.uhn.hapi.fhir:org.hl7.fhir.dstu20.0.1 ... 6.9.9 (391 versions)
  • every version up to 6.9.10: fixed in 6.9.10
—
ca.uhn.hapi.fhir:org.hl7.fhir.validation0.0.1 ... 6.9.9 (391 versions)
  • every version up to 6.9.10: fixed in 6.9.10
—
ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli4.0.0 ... 5.0.0 (7 versions)
  • every version up to 6.9.10: fixed in 6.9.10
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 30× 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.

Showing the most recent 100 of 137 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:18 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:26 UTCEPSS rescore
  8. 2026-10-03 05:09 UTCOSV refresh
  9. 2026-10-02 17:56 UTCEPSS rescore
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-29 15:22 UTCEPSS rescore
  13. 2026-09-28 13:51 UTCEPSS rescore
  14. 2026-09-27 13:48 UTCEPSS rescore
  15. 2026-09-26 15:59 UTCEPSS rescore
  16. 2026-09-24 14:04 UTCEPSS rescore
  17. 2026-09-23 17:54 UTCEPSS rescore
  18. 2026-09-20 20:16 UTCEPSS rescore
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-17 19:31 UTCEPSS rescore
  21. 2026-09-16 14:08 UTCEPSS rescore
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-15 03:11 UTCEPSS rescore
  24. 2026-09-14 02:22 UTCEG score recompute
  25. 2026-09-14 02:22 UTCVendor advisory
Show 75 more
  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-13 14:08 UTCEG score recompute
  3. 2026-09-13 14:08 UTCVendor advisory
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-10 09:35 UTCEPSS rescore
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-02 14:12 UTCEPSS rescore
  11. 2026-09-01 13:54 UTCEPSS rescore
  12. 2026-09-01 04:40 UTCEPSS rescore
  13. 2026-08-30 21:17 UTCEG score recompute
  14. 2026-08-30 21:17 UTCVendor advisory
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-24 22:22 UTCEG score recompute
  22. 2026-08-24 22:22 UTCVendor advisory
  23. 2026-08-24 05:18 UTCVendor advisory
  24. 2026-08-23 15:32 UTCVendor advisory
  25. 2026-08-23 04:02 UTCEG score recompute
  26. 2026-08-23 04:02 UTCVendor advisory
  27. 2026-08-23 00:19 UTCEPSS rescore
  28. 2026-08-21 23:49 UTCEPSS rescore
  29. 2026-08-21 18:53 UTCVendor advisory
  30. 2026-08-21 07:23 UTCEG score recompute
  31. 2026-08-21 07:23 UTCVendor advisory
  32. 2026-08-20 22:55 UTCEPSS rescore
  33. 2026-08-20 19:41 UTCVendor advisory
  34. 2026-08-20 08:12 UTCEG score recompute
  35. 2026-08-20 08:12 UTCVendor advisory
  36. 2026-08-19 17:04 UTCEPSS rescore
  37. 2026-08-19 08:08 UTCEG score recompute
  38. 2026-08-19 08:08 UTCVendor advisory
  39. 2026-08-18 13:48 UTCEPSS rescore
  40. 2026-08-17 13:47 UTCEPSS rescore
  41. 2026-08-17 08:21 UTCVendor advisory
  42. 2026-08-16 20:52 UTCEG score recompute
  43. 2026-08-16 20:52 UTCVendor advisory
  44. 2026-08-16 14:56 UTCEPSS rescore
  45. 2026-08-16 08:56 UTCEG score recompute
  46. 2026-08-16 08:56 UTCVendor advisory
  47. 2026-08-16 02:14 UTCEPSS rescore
  48. 2026-08-15 21:24 UTCVendor advisory
  49. 2026-08-15 09:10 UTCEG score recompute
  50. 2026-08-15 09:10 UTCVendor advisory
  51. 2026-08-15 01:30 UTCEPSS rescore
  52. 2026-08-14 20:48 UTCVendor advisory
  53. 2026-08-14 09:19 UTCEG score recompute
  54. 2026-08-14 09:19 UTCVendor advisory
  55. 2026-08-13 22:00 UTCEPSS rescore
  56. 2026-08-12 22:34 UTCEG score recompute
  57. 2026-08-12 13:51 UTCEPSS rescore
  58. 2026-08-11 23:35 UTCEG score recompute
  59. 2026-08-11 00:36 UTCEG score recompute
  60. 2026-08-11 00:00 UTCEPSS rescore
  61. 2026-08-09 14:07 UTCEG score recompute
  62. 2026-08-09 13:46 UTCEPSS rescore
  63. 2026-08-09 02:38 UTCEG score recompute
  64. 2026-08-08 16:37 UTCEPSS rescore
  65. 2026-08-08 03:39 UTCEG score recompute
  66. 2026-08-06 17:11 UTCEG score recompute
  67. 2026-08-06 13:47 UTCEPSS rescore
  68. 2026-08-06 05:41 UTCEG score recompute
  69. 2026-08-05 19:17 UTCEPSS rescore
  70. 2026-08-04 15:25 UTCEG score recompute
  71. 2026-08-04 15:10 UTCEPSS rescore
  72. 2026-08-04 10:39 UTCEPSS rescore
  73. 2026-08-03 20:15 UTCEG score recompute
  74. 2026-08-03 10:36 UTCEPSS rescore
  75. 2026-08-02 08:10 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

Same product

9 shown

Maven:ca.uhn.hapi.fhir:org.hl7.fhir.convertors · Maven:ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 · Maven:ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli

Frequently asked(5)

What is CVE-2026-55470?
CVE-2026-55470 is a high vulnerability published on June 17, 2026. HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. Prior to 6.9.10, the fix for CVE-2026-45367 incompletely patched the DSTU2 module, leaving FHIRPathEngine.matches() in org.hl7.fhir.dstu2/utils/FHIRPathEngine.java to call raw String.matches(sw)…
When was CVE-2026-55470 disclosed?
CVE-2026-55470 was first published on June 17, 2026, with the most recent update on July 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55470 actively exploited?
CVE-2026-55470 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55470?
CVE-2026-55470 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55470?
A fix for CVE-2026-55470 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55470 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55470

Explore →

Is Your Infrastructure Affected by CVE-2026-55470?

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

Book a Demo →Browse All CVEs