CVE-2025-24363

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

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.

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.

CVE-2025-24363 has a CVSS score of 4.2 (Medium). The vector is requires local access, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.8.9); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

This problem has been patched in release 1.8.9

1. What is CVE-2025-24363? CVE-2025-24363 is a medium-severity security vulnerability in org.hl7.fhir.publisher:org.hl7.fhir.publisher.core (maven), affecting versions < 1.8.9. It is fixed in 1.8.9.
2. How severe is CVE-2025-24363? CVE-2025-24363 has a CVSS score of 4.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-24363?
   • org.hl7.fhir.publisher:org.hl7.fhir.publisher.core (maven) (versions < 1.8.9)
   • org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli (maven) (versions < 1.8.9)
4. Is there a fix for CVE-2025-24363? Yes. CVE-2025-24363 is fixed in 1.8.9. Upgrade to this version or later.
5. Is CVE-2025-24363 exploitable, and should I be worried? Whether CVE-2025-24363 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-24363 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-24363?
   • Upgrade org.hl7.fhir.publisher:org.hl7.fhir.publisher.core to 1.8.9 or later
   • Upgrade org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli to 1.8.9 or later

Other vulnerabilities in org.hl7.fhir.publisher:org.hl7.fhir.publisher.core