CVE-2026-45367

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.5%, top 60% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

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

HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. Prior to 6.9.7, the FHIRPathEngine implementation passes user-controlled regular expressions from matches(), matchesFull(), and replaceMatches() to Java regex operations without effective timeouts, allowing catastrophic backtracking and denial of service. This issue is fixed in version 6.9.7.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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 computed
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
51%
KEV
Not listed

Published

May 18, 2026

Last Modified

July 18, 2026

Advisory Details (6)

Auto-updated Jul 16, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available

ReDoS via FHIRPath matches()/replaceMatches() in FHIR Validator HTTP Endpoint · Advisory · hapifhir/org.hl7.fhir.core · GitHub

https://github.com/hapifhir/org.hl7.fhir.core/security/advisories/GHSA-3653-68v6-rq57
github_release Patch Available

6.9.7

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

https://github.com/hapifhir/org.hl7.fhir.core/releases/tag/6.9.7
github_pr Patch Available

Add timeout in funcReplaceMatches in r4, r4b, r5

Patch available: hapifhir/org.hl7.fhir.core 6.9.9 (PR #2463 merged 2026-05-29)

https://github.com/hapifhir/org.hl7.fhir.core/pull/2463
github_pr Patch Available

Add RegexTimeout utilities class

Patch available: hapifhir/org.hl7.fhir.core 6.9.7 (PR #2403 merged 2026-04-19)

https://github.com/hapifhir/org.hl7.fhir.core/pull/2403
github_commit Patch Available

commit e08982d2b6f6 (hapifhir/org.hl7.fhir.core)

Patch available: hapifhir/org.hl7.fhir.core 6.9.9 (contains commit e08982d2b6f6)

https://github.com/hapifhir/org.hl7.fhir.core/commit/e08982d2b6f6dcd6c670a762d9cf999179fbe4ed
github_commit Patch Available

commit 275d015c680c (hapifhir/org.hl7.fhir.core)

Patch available: hapifhir/org.hl7.fhir.core 6.9.7 (contains commit 275d015c680c)

https://github.com/hapifhir/org.hl7.fhir.core/commit/275d015c680ce9f90cbe285596e50118e472bf24

Vendor Advisories for CVE-2026-45367(1)

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

Affected Packages

(8 across 1 ecosystem)
Maven(8)
PackageVulnerable rangeFixed inDependents
ca.uhn.hapi.fhir:org.hl7.fhir.dstu20.0.1 ... 6.9.6 (386 versions)6.9.7—
ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may0.0.1 ... 6.9.6 (386 versions)6.9.7—
ca.uhn.hapi.fhir:org.hl7.fhir.dstu30.0.1 ... 6.9.6 (386 versions)6.9.7—
ca.uhn.hapi.fhir:org.hl7.fhir.r40.0.1 ... 6.9.6 (386 versions)6.9.7—
ca.uhn.hapi.fhir:org.hl7.fhir.r4b5.6.100 ... 6.9.6 (259 versions)6.9.7—
ca.uhn.hapi.fhir:org.hl7.fhir.r50.0.1 ... 6.9.6 (386 versions)6.9.7—
ca.uhn.hapi.fhir:org.hl7.fhir.validation0.0.1 ... 6.9.6 (386 versions)6.9.7—
ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli4.0.0 ... 5.0.0 (7 versions)6.9.7—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 28× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 09:37 UTCEPSS rescore
  9. 2026-09-11 05:53 UTCOSV refresh
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-23 17:12 UTCEG score recompute
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-21 23:49 UTCEPSS rescore
Show 56 more
  1. 2026-08-21 23:41 UTCEG score recompute
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-20 19:08 UTCEG score recompute
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 10:05 UTCEG score recompute
  8. 2026-08-16 14:56 UTCEPSS rescore
  9. 2026-08-16 03:38 UTCEG score recompute
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 02:11 UTCEG score recompute
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-12 14:38 UTCEG score recompute
  15. 2026-08-12 13:51 UTCEPSS rescore
  16. 2026-08-11 13:56 UTCEG score recompute
  17. 2026-08-11 00:41 UTCEG score recompute
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-09 14:06 UTCEG score recompute
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-09 01:39 UTCEG score recompute
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-08 02:08 UTCEG score recompute
  24. 2026-08-07 01:13 UTCEG score recompute
  25. 2026-08-06 13:47 UTCEPSS rescore
  26. 2026-08-05 21:24 UTCEG score recompute
  27. 2026-08-05 19:17 UTCEPSS rescore
  28. 2026-08-04 15:10 UTCEPSS rescore
  29. 2026-08-04 10:38 UTCEPSS rescore
  30. 2026-08-03 17:05 UTCEG score recompute
  31. 2026-08-03 10:36 UTCEPSS rescore
  32. 2026-08-02 07:05 UTCEG score recompute
  33. 2026-08-02 02:27 UTCEPSS rescore
  34. 2026-08-01 18:23 UTCEG score recompute
  35. 2026-08-01 04:16 UTCEPSS rescore
  36. 2026-07-30 16:28 UTCEPSS rescore
  37. 2026-07-30 01:30 UTCEPSS rescore
  38. 2026-07-28 15:36 UTCEPSS rescore
  39. 2026-07-27 14:13 UTCEPSS rescore
  40. 2026-07-26 14:54 UTCEPSS rescore
  41. 2026-07-26 14:54 UTCEPSS rescore
  42. 2026-07-25 14:18 UTCEPSS rescore
  43. 2026-07-24 14:17 UTCEPSS rescore
  44. 2026-07-23 14:18 UTCEPSS rescore
  45. 2026-07-23 03:16 UTCEG score recompute
  46. 2026-07-22 14:08 UTCEPSS rescore
  47. 2026-07-21 15:24 UTCEPSS rescore
  48. 2026-07-20 17:08 UTCEPSS rescore
  49. 2026-07-19 14:31 UTCEPSS rescore
  50. 2026-07-19 02:29 UTCEPSS rescore
  51. 2026-07-18 10:04 UTCEPSS rescore
  52. 2026-07-18 00:29 UTCOSV refresh
  53. 2026-06-14 23:18 UTCEPSS rescore
  54. 2026-06-13 23:00 UTCEPSS rescore
  55. 2026-06-12 23:12 UTCEPSS rescore
  56. 2026-05-24 06:15 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-45367?
CVE-2026-45367 is a high vulnerability published on May 18, 2026. HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. Prior to 6.9.7, the FHIRPathEngine implementation passes user-controlled regular expressions from matches(), matchesFull(), and replaceMatches() to Java regex operations without effective…
When was CVE-2026-45367 disclosed?
CVE-2026-45367 was first published in the National Vulnerability Database on May 18, 2026, with the most recent update on July 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45367 actively exploited?
CVE-2026-45367 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 48.9% of all scored CVEs.
What is the CVSS score of CVE-2026-45367?
CVE-2026-45367 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-45367?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45367, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-45367?

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

Start Free Scan →Browse All CVEs