Advisory record · GHSA-fxj4-p9xp-37v5

HAPI FHIR: Incomplete fix for CVE-2026-45367: DSTU2 FHIRPathEngine.matches() missing RegexTimeout protection allows ReDoS

CVSS 7.5 HighEPSS 0.0068 · 52nd percentile

Published by the GitHub Advisory Database at 17 Jun 2026, 18:47 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
ca.uhn.hapi.fhir:org.hl7.fhir.dstu2Maven<6.9.106.9.10
ca.uhn.hapi.fhir:org.hl7.fhir.convertorsMaven<6.9.106.9.10
ca.uhn.hapi.fhir:org.hl7.fhir.validationMaven<6.9.106.9.10
ca.uhn.hapi.fhir:org.hl7.fhir.validation.cliMaven<6.9.106.9.10
Identifiers
GHSA-fxj4-p9xp-37v5 · CVE-2026-55470
Weakness (CWE)
CWE-1333
Published
17 Jun 2026
Updated
17 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The Maven package ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 (and the related org.hl7.fhir.convertors, org.hl7.fhir.validation, and org.hl7.fhir.validation.cli modules) is vulnerable in versions before 6.9.10. The DSTU2 FHIRPathEngine matches() function lacks regex timeout protection, so a user-supplied FHIRPath expression with a catastrophically backtracking regular expression can exhaust CPU. No authentication is required. Upgrade to version 6.9.10, where the fix is listed.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0068, the 52nd percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.