MITM based Zip Slip in org.hl7.fhir.publisher:org.hl7.fhir.publisher
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.hl7.fhir.publisher:org.hl7.fhir.publisher 1.2.30), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.hl7.fhir.publisher:org.hl7.fhir.publisher
- Affected
- < 1.2.30
- Fixed in
- 1.2.30
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-xr8x-pxm6-prjg lists affected ranges: Maven org.hl7.fhir.publisher:org.hl7.fhir.publisher >=0 <1.2.30
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.1 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
Impact MITM can enable Zip-Slip. Vulnerability Vulnerability 1: Publisher.java There is no validation that the zip file being unpacked has entries that are not maliciously writing outside of the intended destination directory. https://github.com/HL7/fhir-ig-publisher/blob/87313e92de6dd6cea816449e0edd225e054a7891/org.hl7.fhir.publisher.core/src/main/java/org/hl7/fhir/igtools/publisher/Publisher.java#L3598-L3610 Vulnerability 2: WebSourceProvider.java There is a check for malicious zip entries here, but it is not covered by test cases and could potentially be reverted in future changes. https://github.com/HL7/fhir-ig-publisher/blob/87313e92de6dd6cea816449e0edd225e054a7891/org.hl7.fhir.publisher.core/src/main/java/org/hl7/fhir/igtools/web/WebSourceProvider.java#L104-L112 Vulnerability 3: ZipFetcher.java This retains the path for Zip files in FetchedFile entries, which could later be used to output malicious entries to another compressed file or file system.…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-xr8x-pxm6-prjg
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-xr8x-pxm6-prjg Advisory: MITM based Zip Slip in `org.hl7.fhir.publisher:org.hl7.fhir.publisher` IDs: GHSA-xr8x-pxm6-prjg Record: https://patchnext.com/advisories/ghsa-xr8x-pxm6-prjg (revision 1, source checked 26 Oct 2026, 15:53 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.1) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.hl7.fhir.publisher:org.hl7.fhir.publisher 1.2.30. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.hl7.fhir.publisher:org.hl7.fhir.publisher: affected < 1.2.30; fixed in 1.2.30 ## Suggested inspection (read-only) - Maven org.hl7.fhir.publisher:org.hl7.fhir.publisher: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.hl7.fhir.publisher:org.hl7.fhir.publisher. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-xr8x-pxm6-prjg (GitHub-reviewed advisory GHSA-xr8x-pxm6-prjg lists affected ranges: Maven org.hl7.fhir.publisher:org.hl7.fhir.publisher >=0 <1.2.30) Commands are suggestions: review each one before running it.
Loading voting…