How severe is GHSA-jwh2-ffg4-48xc?

GHSA-jwh2-ffg4-48xc has a CVSS score of 7.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-jwh2-ffg4-48xc?

GHSA-jwh2-ffg4-48xc affects the following packages: io.fabric8:kubernetes-client (Maven), io.fabric8:kubernetes-client (Maven), io.fabric8:kubernetes-client (Maven), io.fabric8:kubernetes-client (Maven). Ecosystems affected: Maven.

How do I fix GHSA-jwh2-ffg4-48xc?

Update io.fabric8:kubernetes-client to 4.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jwh2-ffg4-48xc is resolved across your whole dependency graph.

How do I detect GHSA-jwh2-ffg4-48xc in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.fabric8:kubernetes-client. 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-jwh2-ffg4-48xc 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-jwh2-ffg4-48xc?

O3 pinpoints whether GHSA-jwh2-ffg4-48xc 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-jwh2-ffg4-48xc actively exploited in the wild?

No public exploit code has been indexed for GHSA-jwh2-ffg4-48xc yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-jwh2-ffg4-48xc?

GHSA-jwh2-ffg4-48xc has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 67th 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-jwh2-ffg4-48xc?

GHSA-jwh2-ffg4-48xc 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-jwh2-ffg4-48xc published, and has it been updated?

GHSA-jwh2-ffg4-48xc was published on May 24, 2022 and was last updated on November 8, 2023. 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-jwh2-ffg4-48xc

HIGH

Improper Limitation of a Pathname to a Restricted Directory in Fabric8 Kubernetes Client

Also known asCVE-2021-20218

Published

May 24, 2022

Updated

Nov 8, 2023

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk67th percentile+0.72%

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

4 pkgs affected

☕io.fabric8:kubernetes-client☕io.fabric8:kubernetes-client☕io.fabric8:kubernetes-client☕io.fabric8:kubernetes-client

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

A flaw was found in the fabric8 kubernetes-client in version 4.2.0 and after. This flaw allows a malicious pod/container to cause applications using the fabric8 kubernetes-client copy command to extract files outside the working path. The highest threat from this vulnerability is to integrity and system availability. This has been fixed in kubernetes-client-4.13.2 kubernetes-client-5.0.2 kubernetes-client-4.11.2 kubernetes-client-4.7.2

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`io.fabric8:kubernetes-client`	≥ 4.2.0&&< 4.7.2	4.7.2
☕Maven	`io.fabric8:kubernetes-client`	≥ 4.8.0&&< 4.11.2	4.11.2
☕Maven	`io.fabric8:kubernetes-client`	≥ 4.12.0&&< 4.13.2	4.13.2
☕Maven	`io.fabric8:kubernetes-client`	≥ 5.0.0&&< 5.0.2	5.0.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.fabric8:kubernetes-client. 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 io.fabric8:kubernetes-client to 4.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jwh2-ffg4-48xc 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-jwh2-ffg4-48xc 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-jwh2-ffg4-48xc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A flaw was found in the fabric8 kubernetes-client in version 4.2.0 and after. This flaw allows a malicious pod/container to cause applications using the fabric8 kubernetes-client `copy` command to extract files outside the working path. The highest threat from this vulnerability is to integrity and system availability. This has been fixed in kubernetes-client-4.13.2 kubernetes-client-5.0.2 kubernetes-client-4.11.2 kubernetes-client-4.7.2

O3 Security · Impact-Aware SCA

Is GHSA-jwh2-ffg4-48xc in your dependencies?

O3 detects GHSA-jwh2-ffg4-48xc 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