CVE-2026-34361: hapifhir org.hl7.fhir.core · Exposed Files or Directories
Affects hapifhir org.hl7.fhir.coreSource CVE Database V5
Not known to be exploited · CVSS 9.3 Critical : upgrade to 6.9.4 as a priority.
Data as of 30 Oct 2026, 11:52 UTC
Contested
Critical score, yet low EPSS after six months- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.9.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 31 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade hapifhir org.hl7.fhir.core to 6.9.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| hapifhirorg.hl7.fhir.core | Affected
| Fixed in
|
Mavenorg.hl7.fhir.corepkg:maven/org.hl7.fhir.coreOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Organizations should immediately upgrade all HAPI FHIR deployments to version 6.9.4 or later, where this vulnerability is patched. Until upgrades are completed, restrict access to the /loadIG endpoint using network-level controls such as firewalls or API gateways to prevent unauthenticated external access. Review and audit all configured FHIR server URLs to ensure no prefix-overlapping domains exist that could be exploited. Implement strict validation and allowlisting of outbound HTTP requests initiated by the FHIR Validator service. Rotate all authentication tokens (Bearer, Basic, API keys) used by FHIR clients and servers after patching to invalidate any potentially stolen credentials. Employ monitoring and alerting for unusual outbound HTTP requests and token usage patterns. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests targeting the vulnerable endpoint. Educate development and security teams about secure URL matching practices to avoid similar logic flaws in future implementations. Finally, conduct penetration testing and code reviews focused on authentication token handling and external request mechanisms.
Description
HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. Prior to version 6.9.4, the FHIR Validator HTTP service exposes an unauthenticated "/loadIG" endpoint that makes outbound HTTP requests to attacker-controlled URLs. Combined with a startsWith() URL prefix matching flaw in the credential provider (ManagedWebAccessUtils.getServer()), an attacker can steal authentication tokens (Bearer, Basic, API keys) configured for legitimate FHIR servers by registering a domain that prefix-matches a configured server URL. This issue has been patched in version 6.9.4.