How severe is GHSA-6729-95v3-pjc2?

GHSA-6729-95v3-pjc2 has a CVSS score of 4.2/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-6729-95v3-pjc2?

GHSA-6729-95v3-pjc2 affects the following packages: org.hl7.fhir.publisher:org.hl7.fhir.publisher.core (Maven), org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli (Maven). Ecosystems affected: Maven.

How do I fix GHSA-6729-95v3-pjc2?

Update org.hl7.fhir.publisher:org.hl7.fhir.publisher.core to 1.8.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6729-95v3-pjc2 is resolved across your whole dependency graph.

How do I detect GHSA-6729-95v3-pjc2 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.core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6729-95v3-pjc2 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-6729-95v3-pjc2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6729-95v3-pjc2 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-6729-95v3-pjc2?

GHSA-6729-95v3-pjc2 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 7th 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-6729-95v3-pjc2?

GHSA-6729-95v3-pjc2 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6729-95v3-pjc2 published, and has it been updated?

GHSA-6729-95v3-pjc2 was published on January 24, 2025 and was last updated on January 24, 2025. 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

MEDIUM severity

HL7 FHIR IG Publisher potentially exposes GitHub repo user and credential informationGHSA-6729-95v3-pjc2

MEDIUMFix: HL7/fhir-ig-publisher@d968694

GHSA-6729-95v3-pjc2 is a medium-severity (CVSS 4.2) Information Exposure vulnerability in org.hl7.fhir.publisher:org.hl7.fhir.publisher.core. A fix is available for org.hl7.fhir.publisher:org.hl7.fhir.publisher.core — see the affected versions and patch details below.

Also known asCVE-2025-24363

Published

Jan 24, 2025

Updated

Jan 24, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-6729-95v3-pjc2.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk-0.00%

Lower risk than most CVEs7th percentile — riskier than 7% 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.core☕org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli

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

In CI contexts, the IG Publisher CLI uses git commands to determine the URL of the originating repo. If the repo was cloned, or otherwise set to use a repo that uses a username and credential based URL, the entire URL will be included in the built Implementation Guide, exposing username and credential. This does not impact users that clone public repos without credentials, such as those using the auto-ig-build continuous integration infrastructure.

Patches

This problem has been patched in release 1.8.9

Workarounds

Users should update to 1.8.9 or the latest release

Users should ensure the IG repo they are publishing does not have username or credentials included in the origin URL. Running the command git remote origin url should return a URL that contains no username, password, or token.

Users should run the IG Publisher CLI with the -repo parameter and specify a URL that contains no username, password, or token.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.hl7.fhir.publisher:org.hl7.fhir.publisher.core`	all versions	1.8.9`org.hl7.fhir.publisher:org.hl7.fhir.publisher.core:1.8.9`
☕Maven	`org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli`	all versions	1.8.9`org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli:1.8.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.hl7.fhir.publisher:org.hl7.fhir.publisher.core, 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.core to 1.8.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6729-95v3-pjc2 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### Impact In CI contexts, the IG Publisher CLI uses git commands to determine the URL of the originating repo. If the repo was cloned, or otherwise set to use a repo that uses a username and credential based URL, the entire URL will be included in the built Implementation Guide, exposing username and credential. This does not impact users that clone public repos without credentials, such as those using the auto-ig-build continuous integration infrastructure. ### Patches This problem has been patched in release [1.8.9](https://github.com/HL7/fhir-ig-publisher/releases/tag/1.8.9) ### Workarou