CVE-2026-45367: HAPI FHIR: ReDoS via FHIRPath matches()/replaceMatches() in FHIR Validator HTTP Endpoint
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.
Security readout for executives and security teams
Plain-English summary
This vulnerability can let an unauthenticated remote user make affected HAPI FHIR validation services consume excessive CPU by submitting costly regular expressions through FHIRPath functions. The business impact is service disruption, especially for healthcare systems that expose FHIR validation over HTTP.
Executive priority
Treat as high priority for healthcare interoperability services with exposed validation endpoints. The likely business risk is outage or degraded clinical integration workflows, not confidentiality compromise. Patch promptly where external users can submit validation requests.
Technical view
Before org.hl7.fhir.core 6.9.7, FHIRPathEngine passed user-controlled patterns from matches(), matchesFull(), and replaceMatches() into Java regex operations without effective timeout protection. Catastrophic backtracking can cause denial of service. CVSS 3.1 is 7.5, network reachable, low complexity, no privileges, no user interaction.
Likely exposure
Systems using hapifhir org.hl7.fhir.core below 6.9.7 are exposed, especially if FHIR Validator HTTP endpoints accept untrusted validation requests. Exposure depends on whether those FHIRPath functions are reachable through deployed validation workflows.
Exploitation context
The source bundle does not cite active exploitation, and KEV status is false. The described attack path is remote denial of service through crafted FHIRPath regular expression inputs, not data theft or code execution.
Researcher notes
Evidence supports a ReDoS in FHIRPath regex handling and a fixed release at 6.9.7. The bundle identifies commits and pull requests, but does not establish exploitation in the wild or name additional affected downstream products.
Mitigation direction
Upgrade hapifhir org.hl7.fhir.core to version 6.9.7 or later.
Prioritize internet-facing or unauthenticated FHIR Validator HTTP endpoints.
Restrict access to validation endpoints until the fixed version is deployed.
Check the GitHub advisory and release notes for vendor-specific guidance.
Monitor validation services for CPU exhaustion or request latency spikes.
Validation and detection
Inventory applications and services using org.hl7.fhir.core.
Confirm dependency versions are 6.9.7 or later in build outputs.
Identify whether FHIR Validator HTTP endpoints are publicly reachable.
Review logs for repeated slow or failed validation requests.
Retest availability after upgrading under normal validation workload.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-1333: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-1333 · source CWE mapping
Inefficient Regular Expression Complexity
Inefficient Regular Expression Complexity represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.