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

O3 pinpoints whether GHSA-2hcm-q3f4-fjgw 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-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 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

Fix: google/osv-scalibr@2444419

GHSA-2hcm-q3f4-fjgw is a CWE-427 vulnerability in github.com/google/osv-scalibr. O3 Security confirms whether GHSA-2hcm-q3f4-fjgw is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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 Aug 7, 2025 · OSV.dev, NVD, 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

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. 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/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
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-2hcm-q3f4-fjgw 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-2hcm-q3f4-fjgw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

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

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