Skip to content
Fencer Intel
medium 4.2

CVE-2025-24363 json

The HL7 FHIR IG publisher may potentially expose GitHub repo user and credential information

published last yr. modified 4mo ago also EUVD-2025-0136 , GHSA-6729-95v3-pjc2

cvss
4.2
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 7%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.hl7.fhir.publisher:org.hl7.fhir.publisher.core 1.8.9
  • maven org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli 1.8.9
  • hl7 fhir_ig_publisher 1.8.9
  • org.hl7.fhir.publisher org.hl7.fhir.publisher.core 1.8.9
  • org.hl7.fhir.publisher org.hl7.fhir.publisher.cli 1.8.9

Is CVE-2025-24363 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.2 CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N
GitHub 3.1 4.2 CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.hl7.fhir.publisher:org.hl7.fhir.publisher.core
<1.8.9
1.8.9
maven org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli
<1.8.9
1.8.9

Affected products

  • HL7 fhir-ig-publisher

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.