How severe is GHSA-2hcm-q3f4-fjgw?

No CVSS score has been assigned to GHSA-2hcm-q3f4-fjgw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2hcm-q3f4-fjgw?

GHSA-2hcm-q3f4-fjgw affects the following packages: github.com/google/osv-scalibr (Go). Ecosystems affected: Go.

How do I fix GHSA-2hcm-q3f4-fjgw?

Update github.com/google/osv-scalibr to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2hcm-q3f4-fjgw is resolved across your whole dependency graph.

How do I detect GHSA-2hcm-q3f4-fjgw in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/google/osv-scalibr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2hcm-q3f4-fjgw if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-2hcm-q3f4-fjgw actively exploited in the wild?

No public exploit code has been indexed for GHSA-2hcm-q3f4-fjgw 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-2hcm-q3f4-fjgw?

GHSA-2hcm-q3f4-fjgw has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 11th 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-2hcm-q3f4-fjgw?

GHSA-2hcm-q3f4-fjgw is classified as CWE-427 (CWE-427), Path Traversal (CWE-22). These weakness types 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-2hcm-q3f4-fjgw published, and has it been updated?

GHSA-2hcm-q3f4-fjgw was published on June 18, 2025 and was last updated on August 7, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-2hcm-q3f4-fjgw — osv-scalibr

Fix: google/osv-scalibr@2444419

GHSA-2hcm-q3f4-fjgw is a CWE-427 vulnerability in github.com/google/osv-scalibr. A fix is available for github.com/google/osv-scalibr — see the affected versions and patch details below.

OSV-SCALIBR's Container Image Unpacking Vulnerable to Arbitrary File Write via Path Traversal

Also known asCVE-2025-5981GO-2025-3767

Published

Jun 18, 2025

Updated

Aug 7, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 GHSA-2hcm-q3f4-fjgw.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs11th percentile — riskier than 11% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/google/osv-scalibr

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

Arbitrary file write as the OSV-SCALIBR user on the host system via a path traversal vulnerability when using OSV-SCALIBR's unpack() function for container images. Particularly, when using the CLI flag --remote-image on untrusted container images.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/google/osv-scalibr`	≥ 0.1.3&&< 0.2.1	0.2.1`go get github.com/google/osv-scalibr@v0.2.1`

Affected Products

1 product · 1 configurations

Application

osv-scalibrgoogle

≥ 0.1.3 && < 0.1.8

range

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/google/osv-scalibr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/google/osv-scalibr to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2hcm-q3f4-fjgw is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-2hcm-q3f4-fjgw in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works