Skip to main content
VulnerabilityPublished Updated

CVE-2024-51132: hapi-fhir · An XML External Entity (XXE)

Affects hapi-fhirSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 6.4.0 as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.9% chance of exploitation in 30 days – higher than 79% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.4.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade org.hl7.fhir.core/hapi-fhir to 6.4.0.

Affected software

ProductAffectedFixed in
Mavenorg.hl7.fhir.core/hapi-fhirpkg:maven/org.hl7.fhir.core/hapi-fhirOther threatsAffected
  • <6.4.0
Fixed in
  • 6.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-51132, organizations should immediately upgrade HAPI FHIR to version 6.4.0 or later once the patch is officially released. Until then, applying temporary mitigations such as disabling XML external entity processing in XML parsers used by HAPI FHIR can reduce risk. Implement strict input validation and sanitization to reject malicious XML payloads. Employ network-level protections such as web application firewalls (WAFs) configured to detect and block XXE attack patterns. Conduct thorough security testing and code reviews focusing on XML processing components. Monitor logs for unusual XML entity references or unexpected file access attempts. Isolate HAPI FHIR servers within segmented network zones to limit potential lateral movement. Educate development and operations teams about secure XML handling practices. Finally, maintain up-to-date backups and incident response plans tailored to healthcare data breaches to ensure rapid recovery if exploitation occurs.

Description

An XML External Entity (XXE) vulnerability in HAPI FHIR before v6.4.0 allows attackers to access sensitive information or execute arbitrary code via supplying a crafted request containing malicious XML entities.

References

Community reviews

Loading reviews…