HL7 FHIR IG Publisher potentially exposes GitHub repo user and credential information

Exploitation

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

CVSS

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

EPSS

• CVE-2025-24363: 0.18% estimated exploitation activity in the next 30 days; percentile 7.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 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 OR 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. OR Users should run the IG Publisher CLI with the -repo parameter and specify a URL that contains no username, password, or token.

Published by the source

24 Jan 2025, 20:40 UTC

Last modified by the source

24 Jan 2025, 21:40 UTC

Source last checked

26 Oct 2026, 16:34 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6729-95v3-pjc2

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

# Patch Next advisory brief: CVE-2025-24363

Advisory: HL7 FHIR IG Publisher potentially exposes GitHub repo user and credential information
IDs: CVE-2025-24363, GHSA-6729-95v3-pjc2
Record: https://patchnext.com/advisories/cve-2025-24363 (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: Medium (CVSS 4.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli 1.8.9; org.hl7.fhir.publisher:org.hl7.fhir.publisher.core 1.8.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli: affected < 1.8.9; fixed in 1.8.9
- Maven org.hl7.fhir.publisher:org.hl7.fhir.publisher.core: affected < 1.8.9; fixed in 1.8.9

## Suggested inspection (read-only)
- Maven org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli: check the installed version with your package manager.
- Maven org.hl7.fhir.publisher:org.hl7.fhir.publisher.core: 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.hl7.fhir.publisher:org.hl7.fhir.publisher.cli, org.hl7.fhir.publisher:org.hl7.fhir.publisher.core.
- 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-6729-95v3-pjc2 (GitHub-reviewed advisory GHSA-6729-95v3-pjc2 lists affected ranges: Maven org.hl7.fhir.publisher:org.hl7.fhir.publisher.core >=0 =0 <1.8.9)

Commands are suggestions: review each one before running it.