How severe is GHSA-8c3x-hq82-gjcm?

GHSA-8c3x-hq82-gjcm has a CVSS score of 8.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-8c3x-hq82-gjcm?

GHSA-8c3x-hq82-gjcm affects the following packages: org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli (Maven), org.hl7.fhir.publisher:org.hl7.fhir.publisher.core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-8c3x-hq82-gjcm?

Update org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli to 1.7.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8c3x-hq82-gjcm is resolved across your whole dependency graph.

How do I detect GHSA-8c3x-hq82-gjcm in my Maven dependencies?

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

How do I mitigate GHSA-8c3x-hq82-gjcm 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-8c3x-hq82-gjcm actively exploited in the wild?

No public exploit code has been indexed for GHSA-8c3x-hq82-gjcm 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-8c3x-hq82-gjcm?

GHSA-8c3x-hq82-gjcm 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-8c3x-hq82-gjcm?

GHSA-8c3x-hq82-gjcm 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-8c3x-hq82-gjcm published, and has it been updated?

GHSA-8c3x-hq82-gjcm was published on January 24, 2025 and was last updated on February 3, 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

XXE vulnerability in XSLT parsing in `org.hl7.fhir.publisher`GHSA-8c3x-hq82-gjcm

HIGHFix: HL7/fhir-ig-publisher@3560de2

GHSA-8c3x-hq82-gjcm is a high-severity (CVSS 8.6) XML External Entity (XXE) vulnerability in org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli. A fix is available for org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli — see the affected versions and patch details below.

Also known asCVE-2024-52807

Published

Jan 24, 2025

Updated

Feb 3, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

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

2 pkgs affected

☕org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli☕org.hl7.fhir.publisher:org.hl7.fhir.publisher.core

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

XSLT transforms 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.publisher is being used to within a host where external clients can submit XML.

A previous release provided an incomplete solution revealed by new testing.

Patches

This issue has been patched as of version 1.7.4

Workarounds

None

References

Previous Advisory for Incomplete solution MITRE CWE OWASP XML External Entity Prevention Cheat Sheet

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli`	all versions	1.7.4`org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli:1.7.4`
☕Maven	`org.hl7.fhir.publisher:org.hl7.fhir.publisher.core`	all versions	1.7.4`org.hl7.fhir.publisher:org.hl7.fhir.publisher.core:1.7.4`

Detection & mitigation playbook

Open-source dependency

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

Frequently Asked Questions

### Impact XSLT transforms 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.publisher is being used to within a host where external clients can submit XML. A previous release provided an incomplete solution revealed by new testing. ### Patches This issue has been patched as of version 1.7.4 ### Workarounds None ### References [Previous Advisory for Incomplete solution](https://github.com/HL7/fhir-ig-publisher/

O3 Security · Impact-Aware SCA

Is GHSA-8c3x-hq82-gjcm in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

8.6/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Raw vector

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

CWE Classification

CWE-611XML External Entity (XXE)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

fhir-ig-publisher

8.3/10

Code-Review7/10

Maintained10/10

Dependency-Update-Tool10/10

Branch-ProtectionN/A

Vulnerabilities6/10

Assessed Nov 5, 2026

Timeline

Disclosed

Jan 24, 2025

Last updated

Feb 3, 2026

Identifiers

GHSA-8c3x-hq82-gjcm

References

Advisorynvd.nist.gov · CVE 2024 52807 Webgithub.com · GHSA 59rq 22fm x8q5 Webgithub.com · GHSA 8c3x hq82 gjcm Webgithub.com · 3560de2f486d688a3ddcf4aa54d8bdacea380c3d Webgithub.com · 1.7.3...1.7.4 Packagegithub.com · fhir ig publisher

Related vulnerabilities

Also affects org.hl7.fhir.publisher.cli

This CVE is high severity; 1 of 2 other CVEs affecting org.hl7.fhir.publisher.cli is rated as high or higher (top: high).

CVE-2025-24363CVE-2024-52807

Same weakness: CWE-611

This CVE is high severity; 6 of 6 other CVEs with CWE-611 are rated as high or higher (top: critical).

CVE-2026-108358CVE-2026-108357CVE-2026-61586CVE-2026-61741CVE-2026-61570CVE-2026-55848Browse all CWE-611

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 3, 2026