Skip to content
Fencer Intel
high 7.5

CVE-2026-45367 json

HAPI FHIR: ReDoS via FHIRPath matches()/replaceMatches() in FHIR Validator HTTP Endpoint

published 5mo ago modified 16d ago also EUVD-2026-44983 , GHSA-3653-68v6-rq57

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 6.9.7
  • maven ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may 6.9.7
  • maven ca.uhn.hapi.fhir:org.hl7.fhir.dstu3 6.9.7
  • maven ca.uhn.hapi.fhir:org.hl7.fhir.r4 6.9.7
  • maven ca.uhn.hapi.fhir:org.hl7.fhir.r4b 6.9.7
  • maven ca.uhn.hapi.fhir:org.hl7.fhir.r5 6.9.7
  • maven ca.uhn.hapi.fhir:org.hl7.fhir.validation 6.9.7
  • maven ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli 6.9.7
  • ca.uhn.hapi.fhir org.hl7.fhir.utilities 6.9.7
  • hapifhir hl7_fhir_core 6.9.7

Is CVE-2026-45367 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-45367 updated cvss 7.5

ca.uhn.hapi.fhir/org.hl7.fhir.r4: HAPI FHIR: Denial of Service via uncontrolled regular expression processing

  • Red Hat build of Apache Camel 4 for Quarkus 3 org.hl7.fhir.r4 6.9.12
    affected: no fix available
  • Red Hat Fuse 7 org.hl7.fhir.r4 6.9.12
    affected: no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
3mo ago

Exploit prediction

0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven ca.uhn.hapi.fhir:org.hl7.fhir.dstu2
<6.9.7
6.9.7
maven ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may
<6.9.7
6.9.7
maven ca.uhn.hapi.fhir:org.hl7.fhir.dstu3
<6.9.7
6.9.7
maven ca.uhn.hapi.fhir:org.hl7.fhir.r4
<6.9.7
6.9.7
maven ca.uhn.hapi.fhir:org.hl7.fhir.r4b
<6.9.7
6.9.7
maven ca.uhn.hapi.fhir:org.hl7.fhir.r5
<6.9.7
6.9.7
maven ca.uhn.hapi.fhir:org.hl7.fhir.validation
<6.9.7
6.9.7
maven ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli
<6.9.7
6.9.7

Affected products

  • hapifhir org.hl7.fhir.core

Classification

Weakness
  • CWE-1333 Inefficient Regular Expression Complexity

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.