HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. Prior to 6.9.9 and 6.9.4.2, all implementations of FHIRPathEngine accept arbitrary FHIRPath expressions and evaluate them without input validation, and the FHIRPath functions matches(), matchesFull(), and replaceMatches() pass user-controlled regular expressions to Java's Pattern.compile() and String.replaceAll() through an incomplete timeout utility. An attacker can send a resource containing an evil regex pattern that causes catastrophic backtracking, exhausting CPU resources and causing denial of service in the FHIR Validator HTTP endpoint and affected org.hl7.fhir.* modules. This issue is fixed in versions 6.9.9 and 6.9.4.2.
CVE-2026-49485
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 52% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 49(Track)EG Risk 49/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation1% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 48.4%
- KEV
- Not listed
Published
July 9, 2026
Last Modified
July 23, 2026
Advisory Details (6)
Auto-updated Jul 17, 20266.9.9
Patch available: hapifhir/org.hl7.fhir.core 6.9.9
https://github.com/hapifhir/org.hl7.fhir.core/releases/tag/6.9.96.9.4.2
Patch available: hapifhir/org.hl7.fhir.core 6.9.4.2
https://github.com/hapifhir/org.hl7.fhir.core/releases/tag/6.9.4.2commit e08982d2b6f6 (hapifhir/org.hl7.fhir.core)
Patch available: hapifhir/org.hl7.fhir.core 6.9.9 (contains commit e08982d2b6f6)
https://github.com/hapifhir/org.hl7.fhir.core/commit/e08982d2b6f6dcd6c670a762d9cf999179fbe4edcommit 109c88837c03 (hapifhir/org.hl7.fhir.core)
Patch available: hapifhir/org.hl7.fhir.core 6.9.4.2 (contains commit 109c88837c03)
https://github.com/hapifhir/org.hl7.fhir.core/commit/109c88837c032ef399b2eb87ddde86692065cf41Add timeout in funcReplaceMatches in r4, r4b, r5
Patch available: hapifhir/org.hl7.fhir.core 6.9.9 (PR #2463 merged 2026-05-29)
https://github.com/hapifhir/org.hl7.fhir.core/pull/2463ReDoS via FHIRPath matches()/replaceMatches() in FHIR Validator HTTP Endpoint · Advisory · hapifhir/org.hl7.fhir.core · GitHub
https://github.com/hapifhir/org.hl7.fhir.core/security/advisories/GHSA-7cmj-v6x8-frvvVendor Advisories for CVE-2026-49485(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(8 across 1 ecosystem)
Maven(8)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| ca.uhn.hapi.fhir:org.hl7.fhir.dstu2 | 0.0.1 ... 6.9.4.1 (385 versions) | 6.9.4.2 | — |
| ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may | 0.0.1 ... 6.9.4.1 (385 versions) | 6.9.4.2 | — |
| ca.uhn.hapi.fhir:org.hl7.fhir.dstu3 | 0.0.1 ... 6.9.4.1 (385 versions) | 6.9.4.2 | — |
| ca.uhn.hapi.fhir:org.hl7.fhir.r4 | 0.0.1 ... 6.9.4.1 (385 versions) | 6.9.4.2 | — |
| ca.uhn.hapi.fhir:org.hl7.fhir.r4b | 5.6.100 ... 6.9.4.1 (258 versions) | 6.9.4.2 | — |
| ca.uhn.hapi.fhir:org.hl7.fhir.r5 | 0.0.1 ... 6.9.4.1 (385 versions) | 6.9.4.2 | — |
| ca.uhn.hapi.fhir:org.hl7.fhir.validation | 0.0.1 ... 6.9.4.1 (385 versions) | 6.9.4.2 | — |
| ca.uhn.hapi.fhir:org.hl7.fhir.validation.cli | 4.0.0 ... 5.0.0 (7 versions) | 6.9.4.2 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 03:42 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-09 13:45 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-400
Frequently asked(5)
What is CVE-2026-49485?
When was CVE-2026-49485 disclosed?
Is CVE-2026-49485 actively exploited?
What is the CVSS score of CVE-2026-49485?
How do I remediate CVE-2026-49485?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49485
Is Your Infrastructure Affected by CVE-2026-49485?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.