How severe is GHSA-84xv-jfrm-h4gm?

GHSA-84xv-jfrm-h4gm has a CVSS score of 8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-84xv-jfrm-h4gm?

GHSA-84xv-jfrm-h4gm affects the following packages: github.com/devfile/registry-support/registry-library (Go). Ecosystems affected: Go.

How do I fix GHSA-84xv-jfrm-h4gm?

Update github.com/devfile/registry-support/registry-library to 0.0.0-20240206 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84xv-jfrm-h4gm is resolved across your whole dependency graph.

How do I detect GHSA-84xv-jfrm-h4gm in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/devfile/registry-support/registry-library. 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-84xv-jfrm-h4gm 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-84xv-jfrm-h4gm?

O3 pinpoints whether GHSA-84xv-jfrm-h4gm 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-84xv-jfrm-h4gm actively exploited in the wild?

No public exploit code has been indexed for GHSA-84xv-jfrm-h4gm 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-84xv-jfrm-h4gm?

GHSA-84xv-jfrm-h4gm has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 56th 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-84xv-jfrm-h4gm?

GHSA-84xv-jfrm-h4gm 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-84xv-jfrm-h4gm published, and has it been updated?

GHSA-84xv-jfrm-h4gm was published on February 14, 2024 and was last updated on June 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-84xv-jfrm-h4gm: registry-library (High 8)

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk56th percentile-1.17%

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

1 pkg affected

🐹github.com/devfile/registry-support/registry-library

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

A vulnerability was found in the decompression function of registry-support. This issue can be triggered by an unauthenticated remote attacker when tricking a user into opening a specially modified .tar archive, leading to the cleanup process following relative paths to overwrite or delete files outside the intended scope.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/devfile/registry-support/registry-library`	all versions	0.0.0-20240206

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/devfile/registry-support/registry-library. 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 github.com/devfile/registry-support/registry-library to 0.0.0-20240206 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-84xv-jfrm-h4gm 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-84xv-jfrm-h4gm 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-84xv-jfrm-h4gm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A vulnerability was found in the decompression function of registry-support. This issue can be triggered by an unauthenticated remote attacker when tricking a user into opening a specially modified .tar archive, leading to the cleanup process following relative paths to overwrite or delete files outside the intended scope.

O3 Security · Impact-Aware SCA

Is GHSA-84xv-jfrm-h4gm in your dependencies?

O3 detects GHSA-84xv-jfrm-h4gm across Go 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

GHSA-84xv-jfrm-h4gm