How severe is GHSA-w9j7-phm3-f97j?

GHSA-w9j7-phm3-f97j has a CVSS score of 8.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-w9j7-phm3-f97j?

GHSA-w9j7-phm3-f97j affects the following packages: org.fhir:ucum (Maven). Ecosystems affected: Maven.

How do I fix GHSA-w9j7-phm3-f97j?

Update org.fhir:ucum to 1.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w9j7-phm3-f97j is resolved across your whole dependency graph.

How do I detect GHSA-w9j7-phm3-f97j in my Maven dependencies?

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

How do I mitigate GHSA-w9j7-phm3-f97j 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 GHSA-w9j7-phm3-f97j actively exploited in the wild?

No public exploit code has been indexed for GHSA-w9j7-phm3-f97j 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 GHSA-w9j7-phm3-f97j?

GHSA-w9j7-phm3-f97j has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 47th 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 GHSA-w9j7-phm3-f97j?

GHSA-w9j7-phm3-f97j 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 GHSA-w9j7-phm3-f97j published, and has it been updated?

GHSA-w9j7-phm3-f97j was published on December 13, 2024 and was last updated on December 13, 2024. 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

Ucum-java has an XXE vulnerability in XML parsingGHSA-w9j7-phm3-f97j

HIGH

GHSA-w9j7-phm3-f97j is a high-severity (CVSS 8.6) XML External Entity (XXE) vulnerability in org.fhir:ucum. A fix is available for org.fhir:ucum — see the affected versions and patch details below.

Also known asCVE-2024-55887

Published

Dec 13, 2024

Updated

Dec 13, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 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 GHSA-w9j7-phm3-f97j.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs47th percentile — riskier than 47% 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

1 pkg affected

☕org.fhir:ucum

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

Impact

XML parsing performed by the UcumEssenceService is 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 ucum is being used to within a host where external clients can submit XML.

Patches

Release 1.0.9 of ucum fixes this vulnerability

Workarounds

Ensure that the source xml for instantiating UcumEssenceService is trusted.

References

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.fhir:ucum`	all versions	1.0.9`org.fhir:ucum:1.0.9`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.fhir:ucum, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.fhir:ucum to 1.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w9j7-phm3-f97j 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

The FHIR component is not supported in Red Hat Fuse 7 and Red Hat Integration Camel K, so these products are not affected by this vulnerability. This vulnerability is of important severity because it enables XML External Entity (XXE) injection, a important issue that can lead to unauthorized access to sensitive data…

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 GHSA-w9j7-phm3-f97j (CC BY 4.0)

Frequently Asked Questions

### Impact XML parsing performed by the UcumEssenceService is 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 ucum is being used to within a host where external clients can submit XML. ### Patches Release 1.0.9 of ucum fixes this vulnerability ### Workarounds Ensure that the source xml for instantiating UcumEssenceService is trusted. ### References * https://cwe.mitre.org/data/definitions/611.html * https://cheatsheetseries.owasp.org/cheatsheets/XML_External_Entit