Ucum-java has an XXE vulnerability in XML parsing

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2024-55887: 0.56% estimated exploitation activity in the next 30 days; percentile 46.52 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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/XMLExternalEntityPreventionCheatSheet.html#jaxp-documentbuilderfactory-saxparserfactory-and-dom4j

Published by the source

13 Dec 2024, 20:35 UTC

Last modified by the source

13 Dec 2024, 20:36 UTC

Source last checked

26 Oct 2026, 16:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w9j7-phm3-f97j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-55887

Advisory: Ucum-java has an XXE vulnerability in XML parsing
IDs: CVE-2024-55887, GHSA-w9j7-phm3-f97j
Record: https://patchnext.com/advisories/cve-2024-55887 (revision 1, source checked 26 Oct 2026, 16:34 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.fhir:ucum 1.0.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.fhir:ucum: affected < 1.0.9; fixed in 1.0.9

## Suggested inspection (read-only)
- Maven org.fhir:ucum: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.fhir:ucum.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w9j7-phm3-f97j (GitHub-reviewed advisory GHSA-w9j7-phm3-f97j lists affected ranges: Maven org.fhir:ucum >=0 <1.0.9)

Commands are suggestions: review each one before running it.