How severe is GHSA-jqh6-9574-5x22?

GHSA-jqh6-9574-5x22 has a CVSS score of 9.1/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jqh6-9574-5x22?

GHSA-jqh6-9574-5x22 affects the following packages: ca.uhn.hapi.fhir:org.hl7.fhir.core (Maven), ca.uhn.hapi.fhir:org.hl7.fhir.convertors (Maven), ca.uhn.hapi.fhir:org.hl7.fhir.r4b (Maven), ca.uhn.hapi.fhir:org.hl7.fhir.r5 (Maven), ca.uhn.hapi.fhir:org.hl7.fhir.utilities (Maven), ca.uhn.hapi.fhir:org.hl7.fhir.validation (Maven). Ecosystems affected: Maven.

How do I fix GHSA-jqh6-9574-5x22?

Update ca.uhn.hapi.fhir:org.hl7.fhir.core to 5.6.92 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jqh6-9574-5x22 is resolved across your whole dependency graph.

How do I detect GHSA-jqh6-9574-5x22 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ca.uhn.hapi.fhir:org.hl7.fhir.core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-jqh6-9574-5x22 if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-jqh6-9574-5x22?

O3 pinpoints whether GHSA-jqh6-9574-5x22 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-jqh6-9574-5x22 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-jqh6-9574-5x22, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-jqh6-9574-5x22?

GHSA-jqh6-9574-5x22 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 63th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-jqh6-9574-5x22?

GHSA-jqh6-9574-5x22 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-jqh6-9574-5x22 published, and has it been updated?

GHSA-jqh6-9574-5x22 was published on January 23, 2023 and was last updated on March 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-jqh6-9574-5x22

CRITICAL

MITM based Zip Slip in `ca.uhn.hapi.fhir:org.hl7.fhir.core`

Also known asCVE-2023-24057

Published

Jan 23, 2023

Updated

Mar 16, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk63th percentile+0.48%

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.

Blast Radius

6 pkgs affected

☕ca.uhn.hapi.fhir:org.hl7.fhir.core☕ca.uhn.hapi.fhir:org.hl7.fhir.convertors☕ca.uhn.hapi.fhir:org.hl7.fhir.r4b☕ca.uhn.hapi.fhir:org.hl7.fhir.r5☕ca.uhn.hapi.fhir:org.hl7.fhir.utilities☕ca.uhn.hapi.fhir:org.hl7.fhir.validation

Real-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

Impact

MITM can enable Zip-Slip.

Vulnerability

Vulnerability 1: `Scanner.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/hapifhir/org.hl7.fhir.core/blob/8c43e21094af971303131efd081503e5a112db4b/org.hl7.fhir.validation/src/main/java/org/hl7/fhir/validation/Scanner.java#L335-L357

This zip archive is downloaded over HTTP instead of HTTPS, leaving it vulnerable to compromise in-flight. https://github.com/hapifhir/org.hl7.fhir.core/blob/8c43e21094af971303131efd081503e5a112db4b/org.hl7.fhir.validation/src/main/java/org/hl7/fhir/validation/Scanner.java#L136

Vulnerability 2: `TerminologyCacheManager.java`

Note: While these links point to only one implementation, both implementations of TerminologyCacheManager.java are vulnerable to this as their code seems to be duplicated.

While there is validation in this bit of logic that attempts to validate that the zip file doesn't contain malicious entries that escape the destination directory, the guard is insufficient.

https://github.com/hapifhir/org.hl7.fhir.core/blob/f58b7acfb5e393cac52cc5bbb170bdb669c2880e/org.hl7.fhir.r5/src/main/java/org/hl7/fhir/r5/terminologies/TerminologyCacheManager.java#L97-L113

This is because the Utilities.path(String... path) method does not normalize the path, although it seems to be attempting to do so. https://github.com/hapifhir/org.hl7.fhir.core/blob/f58b7acfb5e393cac52cc5bbb170bdb669c2880e/org.hl7.fhir.utilities/src/main/java/org/hl7/fhir/utilities/Utilities.java#L617-L675

The normalization only occurs if the path element starts with a path traversal payload. As an example, calling Utilities.path("/base", "/child/../test") will return the string "/base/child/../test".

This guard logic can, thus, be easily bypassed: https://github.com/hapifhir/org.hl7.fhir.core/blob/f58b7acfb5e393cac52cc5bbb170bdb669c2880e/org.hl7.fhir.r5/src/main/java/org/hl7/fhir/r5/terminologies/TerminologyCacheManager.java#L100-L104

Assuming an attacker can control the return value of ze.getName(), they can supply a value like /anything/../../../../zipsip-protection-bypass.txt.

Similarly, an attacker can control the contents of the Zip file via a MITM attack as this logic is used with resources not downloaded over HTTPS.

https://github.com/hapifhir/org.hl7.fhir.core/blob/f58b7acfb5e393cac52cc5bbb170bdb669c2880e/org.hl7.fhir.r5/src/main/java/org/hl7/fhir/r5/terminologies/TerminologyCacheManager.java#L66-L73

Patches

Unknown

Workarounds

Unknown

References

https://snyk.io/research/zip-slip-vulnerability

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`ca.uhn.hapi.fhir:org.hl7.fhir.core`	all versions	5.6.92
☕Maven	`ca.uhn.hapi.fhir:org.hl7.fhir.convertors`	all versions	5.6.92
☕Maven	`ca.uhn.hapi.fhir:org.hl7.fhir.r4b`	all versions	5.6.92
☕Maven	`ca.uhn.hapi.fhir:org.hl7.fhir.r5`	all versions	5.6.92
☕Maven	`ca.uhn.hapi.fhir:org.hl7.fhir.utilities`	all versions	5.6.92
☕Maven	`ca.uhn.hapi.fhir:org.hl7.fhir.validation`	all versions	5.6.92

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

HL7 (Health Level 7) FHIR Core Libraries before 5.6.92 allow attackers t…

github.comNVDFeb 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ca.uhn.hapi.fhir:org.hl7.fhir.core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ca.uhn.hapi.fhir:org.hl7.fhir.core to 5.6.92 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jqh6-9574-5x22 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 pinpoints whether GHSA-jqh6-9574-5x22 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jqh6-9574-5x22. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact MITM can enable Zip-Slip. ### Vulnerability #### Vulnerability 1: `Scanner.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/hapifhir/org.hl7.fhir.core/blob/8c43e21094af971303131efd081503e5a112db4b/org.hl7.fhir.validation/src/main/java/org/hl7/fhir/validation/Scanner.java#L335-L357 This zip archive is downloaded over HTTP instead of HTTPS, leaving it vulnerable to compromise in-flight. https://github.com/hapifhir/org.hl7.fhir.core/blob/8c43e21094af971303131

O3 Security · Impact-Aware SCA

Is GHSA-jqh6-9574-5x22 in your dependencies?

O3 detects GHSA-jqh6-9574-5x22 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

CVSS Score

9.1/10

CVSS v3 base score

Vector breakdown

AV:Attack Vector

Network

AC:Attack Complexity

Low

PR:Privileges Required

High

UI:User Interaction

None

S:Scope

Changed

C:Confidentiality

High

I:Integrity

High

A:Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

CWE Classification

CWE-22Path Traversal

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

fhir-ig-publisher

8.2/10

Maintained10/10

Code-Review1/10

Vulnerabilities10/10

Dependency-Update-Tool10/10

Branch-ProtectionN/A

Assessed Jun 18, 2026

Timeline

Disclosed

Jan 23, 2023

First exploit

Feb 6, 2023

Last updated

Mar 16, 2026

Identifiers

GHSA-jqh6-9574-5x22

References

Advisorynvd.nist.gov Webgithub.com Webgithub.com Webgithub.com Packagegithub.com

Data from OSV.dev, enriched by O3 Security. Refreshed hourly.

GHSA-jqh6-9574-5x22

EPSS Exploitation Probability

Blast Radius

Description

Impact

Vulnerability

Vulnerability 1: Scanner.java

Vulnerability 2: TerminologyCacheManager.java

Patches

Workarounds

References

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-jqh6-9574-5x22 in your dependencies?

Vulnerability 1: `Scanner.java`

Vulnerability 2: `TerminologyCacheManager.java`