CVE-2025-24363: The HL7 FHIR IG publisher may potentially expose GitHub repo user and credential information
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.
Other sources
The HL7 FHIR IG publisher is a tool to take a set of inputs and create a standard FHIR IG. Prior to version 1.8.9, 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. This problem has been patched in release 1.8.9. Some workarounds are available. 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.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-24363?
CVE-2025-24363 is considered a high severity vulnerability due to the exposure of sensitive repository information.
How do I fix CVE-2025-24363?
To fix CVE-2025-24363, you should upgrade to version 1.8.9 of the HL7 FHIR IG Publisher.
What is the impact of CVE-2025-24363?
The impact of CVE-2025-24363 is that the implementation guide may unintentionally include the entire URL of the originating git repository, potentially exposing sensitive credentials.
Which versions of HL7 FHIR IG Publisher are affected by CVE-2025-24363?
Versions prior to 1.8.9 of the HL7 FHIR IG Publisher are affected by CVE-2025-24363.
What components of the HL7 FHIR IG Publisher are vulnerable due to CVE-2025-24363?
The CLI components 'org.hl7.fhir.publisher.cli' and 'org.hl7.fhir.publisher.core' of the HL7 FHIR IG Publisher are vulnerable in versions below 1.8.9.