Skip to content
Noroxi
CVE-2026-45367· NVD / CVE Program· CNA GitHub_M

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.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Jul 16, 2026
Updated
Jul 18, 2026
EPSS
0.7% · 51th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • hapifhir org.hl7.fhir.core

    • < 6.9.7affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenca.uhn.hapi.fhir:org.hl7.fhir.dstu2before 6.9.76.9.7
Mavenca.uhn.hapi.fhir:org.hl7.fhir.dstu2016maybefore 6.9.76.9.7
Mavenca.uhn.hapi.fhir:org.hl7.fhir.dstu3before 6.9.76.9.7
Mavenca.uhn.hapi.fhir:org.hl7.fhir.r4before 6.9.76.9.7
Mavenca.uhn.hapi.fhir:org.hl7.fhir.r4bbefore 6.9.76.9.7
Mavenca.uhn.hapi.fhir:org.hl7.fhir.r5before 6.9.76.9.7
Mavenca.uhn.hapi.fhir:org.hl7.fhir.validationbefore 6.9.76.9.7
Mavenca.uhn.hapi.fhir:org.hl7.fhir.validation.clibefore 6.9.76.9.7

Same product

hapifhir: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-52007XXE vulnerability in XSLT parsing in `org.hl7.fhir.core`
    34Monitor
  • CVE-2024-45294`org.hl7.fhir.core` XXE vulnerability in XSLT transforms
    34Monitor
  • CVE-2026-81876HAPI FHIR: SHCParser DEFLATE infinite loop causes denial of service
    30Monitor
  • CVE-2026-81875HAPI FHIR: SHCParser unbounded DEFLATE decompression causes denial of service
    30Monitor
  • CVE-2026-62296HAPI FHIR: XHTML narrative parser unbounded recursion causes StackOverflow denial of service
    30Monitor
  • CVE-2026-62295HAPI FHIR: JSON utility parser unbounded recursion causes StackOverflow denial of service
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
hapifhir org.hl7.fhir.core6.9.7 · descriptionVendor (CNA)
Maven:ca.uhn.hapi.fhir:org.hl7.fhir.dstu26.9.7Package registry (OSV)
Maven:ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may6.9.7Package registry (OSV)
Maven:ca.uhn.hapi.fhir:org.hl7.fhir.dstu36.9.7Package registry (OSV)
Maven:ca.uhn.hapi.fhir:org.hl7.fhir.r46.9.7Package registry (OSV)
Maven:ca.uhn.hapi.fhir:org.hl7.fhir.r4b6.9.7Package registry (OSV)
Maven:ca.uhn.hapi.fhir:org.hl7.fhir.r56.9.7Package registry (OSV)
Maven:ca.uhn.hapi.fhir:org.hl7.fhir.validation6.9.7Package registry (OSV)
Maven:ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli6.9.7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-1333 · Inefficient Regular Expression Complexity

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records