CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HHigh (7.5) in hapifhir hl7 fhir core. EPSS 0.7% estimated probability of exploitation activity in the next 30 days. Fixed in ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 6.9.10.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:Hca.uhn.hapi.fhir:org.hl7.fhir.dstu2 (Maven): fixed in 6.9.10ca.uhn.hapi.fhir:org.hl7.fhir.convertors (Maven): fixed in 6.9.10ca.uhn.hapi.fhir:org.hl7.fhir.validation (Maven): fixed in 6.9.10ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli (Maven): fixed in 6.9.10Explain CVE-2026-55470 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-55470?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-55470?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-55470 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| hapifhir:hl7_fhir_core | before 6.9.10 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-fxj4-p9xp-37v5 | Maven | ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 | <6.9.10 | 6.9.10 |
| GHSA-fxj4-p9xp-37v5 | Maven | ca.uhn.hapi.fhir:org.hl7.fhir.convertors | <6.9.10 | 6.9.10 |
| GHSA-fxj4-p9xp-37v5 | Maven | ca.uhn.hapi.fhir:org.hl7.fhir.validation | <6.9.10 | 6.9.10 |
| GHSA-fxj4-p9xp-37v5 | Maven | ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli | <6.9.10 | 6.9.10 |
Red Hat rates this Important.
This flaw is rated as Important because an unauthenticated, remote attacker can exploit an incomplete patch in the HAPI FHIR DSTU2 module. By submitting a specially crafted FHIRPath expression, an attacker can trigger a Regular Expression Denial of Service (ReDoS) attack, leading to significant resource exhaustion and service unavailability on affected systems.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Build of Apache Camel 4.18 for Quarkus 3.33 | org.hl7.fhir.dstu2 | Fixed 2026-08-13 | RHSA-2026:54776 |
| Red Hat build of Apache Camel 4 for Quarkus 3 | org.hl7.fhir.dstu2 | Affected | |
| Red Hat JBoss Enterprise Application Platform Expansion Pack | org.hl7.fhir.dstu2 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-55470.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.