CVE-2025-24363 is a medium-severity (CVSS 4.2) Information Exposure vulnerability in org.hl7.fhir.publisher:org.hl7.fhir.publisher.core. A fix is available for org.hl7.fhir.publisher:org.hl7.fhir.publisher.core — see the affected versions and patch details below.
The HL7 FHIR IG publisher may potentially expose GitHub repo user and credential information
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-24363.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-24363 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.hl7.fhir.publisher:org.hl7.fhir.publisher.core☕org.hl7.fhir.publisher:org.hl7.fhir.publisher.cliReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.hl7.fhir.publisher:org.hl7.fhir.publisher.core | all versions | 1.8.9org.hl7.fhir.publisher:org.hl7.fhir.publisher.core:1.8.9 |
| ☕Maven | org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli | all versions | 1.8.9org.hl7.fhir.publisher:org.hl7.fhir.publisher.cli:1.8.9 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.hl7.fhir.publisher:org.hl7.fhir.publisher.core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.hl7.fhir.publisher:org.hl7.fhir.publisher.core to 1.8.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-24363 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-24363 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-24363. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-24363 in your dependencies?
O3 Security finds CVE-2025-24363 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.