What is CVE-2024-52007?

HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. XSLT parsing performed by various components are vulnerable to XML external entity injections. A processed XML file with a malicious DTD tag ( ]> could produce XML containing data from the host system. This impacts use cases where org.hl7.fhir.core is being used to within a host where external clients can submit XML. This is related to GHSA-6cr6-ph3p-f5rf, in which its fix (#1571 & #1717) was incomplete. This issue has been addressed in

How severe is CVE-2024-52007?

CVE-2024-52007 has a CVSS score of 8.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-52007?

CVE-2024-52007 affects the following packages: ca.uhn.hapi.fhir:org.hl7.fhir.dstu3 (Maven), ca.uhn.hapi.fhir:org.hl7.fhir.r4 (Maven), ca.uhn.hapi.fhir:org.hl7.fhir.r4b (Maven), ca.uhn.hapi.fhir:org.hl7.fhir.r5 (Maven), ca.uhn.hapi.fhir:org.hl7.fhir.utilities (Maven), ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may (Maven). Ecosystems affected: Maven.

How do I fix CVE-2024-52007?

Update ca.uhn.hapi.fhir:org.hl7.fhir.dstu3 to 6.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-52007 is resolved across your whole dependency graph.

How do I detect CVE-2024-52007 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ca.uhn.hapi.fhir:org.hl7.fhir.dstu3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-52007 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2024-52007 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-52007 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-52007?

CVE-2024-52007 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 60th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-52007?

CVE-2024-52007 is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-52007 published, and has it been updated?

CVE-2024-52007 was published on November 8, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2024-52007 — org.hl7.fhir.dstu3

HIGHFix: hapifhir/org.hl7.fhir.core#1717

CVE-2024-52007 is a high-severity (CVSS 8.6) XML External Entity (XXE) vulnerability in ca.uhn.hapi.fhir:org.hl7.fhir.dstu3. A fix is available for ca.uhn.hapi.fhir:org.hl7.fhir.dstu3 — see the affected versions and patch details below.

XXE vulnerability in XSLT parsing in `org.hl7.fhir.core`

Also known asGHSA-gr3c-q7xf-47vh

Published

Nov 8, 2024

Updated

Oct 28, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-52007.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

6 pkgs affected

☕ca.uhn.hapi.fhir:org.hl7.fhir.dstu3☕ca.uhn.hapi.fhir:org.hl7.fhir.r4☕ca.uhn.hapi.fhir:org.hl7.fhir.r4b☕ca.uhn.hapi.fhir:org.hl7.fhir.r5☕ca.uhn.hapi.fhir:org.hl7.fhir.utilities☕ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

HAPI FHIR is a complete implementation of the HL7 FHIR standard for healthcare interoperability in Java. XSLT parsing performed by various components are vulnerable to XML external entity injections. A processed XML file with a malicious DTD tag ( <!DOCTYPE foo [<!ENTITY example SYSTEM "/etc/passwd"> ]> could produce XML containing data from the host system. This impacts use cases where org.hl7.fhir.core is being used to within a host where external clients can submit XML. This is related to GHSA-6cr6-ph3p-f5rf, in which its fix (#1571 & #1717) was incomplete. This issue has been addressed in release version 6.4.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`ca.uhn.hapi.fhir:org.hl7.fhir.dstu3`	all versions	6.4.0`ca.uhn.hapi.fhir:org.hl7.fhir.dstu3:6.4.0`
☕Maven	`ca.uhn.hapi.fhir:org.hl7.fhir.r4`	all versions	6.4.0`ca.uhn.hapi.fhir:org.hl7.fhir.r4:6.4.0`
☕Maven	`ca.uhn.hapi.fhir:org.hl7.fhir.r4b`	all versions	6.4.0`ca.uhn.hapi.fhir:org.hl7.fhir.r4b:6.4.0`
☕Maven	`ca.uhn.hapi.fhir:org.hl7.fhir.r5`	all versions	6.4.0`ca.uhn.hapi.fhir:org.hl7.fhir.r5:6.4.0`
☕Maven	`ca.uhn.hapi.fhir:org.hl7.fhir.utilities`	all versions	6.4.0`ca.uhn.hapi.fhir:org.hl7.fhir.utilities:6.4.0`
☕Maven	`ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may`	all versions	6.4.0`ca.uhn.hapi.fhir:org.hl7.fhir.dstu2016may:6.4.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ca.uhn.hapi.fhir:org.hl7.fhir.dstu3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ca.uhn.hapi.fhir:org.hl7.fhir.dstu3 to 6.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-52007 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This vulnerability is of important severity rather than moderate due to its potential to expose sensitive host data and compromise system integrity. By exploiting the XXE vulnerability, an attacker can read arbitrary files (e.g., `/etc/passwd`), perform Denial of Service (DoS) through resource exhaustion, or even…

Workaround published by Red Hat

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.

Source: Red Hat security advisory for CVE-2024-52007 (CC BY 4.0)