How severe is CVE-2024-47877?

No CVSS score has been assigned to CVE-2024-47877 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-47877?

CVE-2024-47877 affects the following packages: github.com/codeclysm/extract/v3 (Go), github.com/codeclysm/extract/v4 (Go), github.com/codeclysm/extract (Go). Ecosystems affected: Go.

How do I fix CVE-2024-47877?

No patched version of github.com/codeclysm/extract/v3 has shipped for CVE-2024-47877 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2024-47877 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/codeclysm/extract/v3. 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 CVE-2024-47877 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 CVE-2024-47877?

O3 pinpoints whether CVE-2024-47877 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 CVE-2024-47877 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-47877 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 CVE-2024-47877?

CVE-2024-47877 is classified as Path Traversal (CWE-22), CWE-61 (CWE-61). 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 CVE-2024-47877 published, and has it been updated?

CVE-2024-47877 was published on October 11, 2024 and was last updated on July 15, 2026. 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

CVE-2024-47877

Fix: codeclysm/extract@4a98568

CVE-2024-47877 is a Path Traversal vulnerability in github.com/codeclysm/extract/v3. O3 Security confirms whether CVE-2024-47877 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Extract has insufficient checks allowing attacker to create symlinks outside the extraction directory.

Also known asGHSA-8rm2-93mq-jqhcGO-2024-3196

Published

Oct 11, 2024

Updated

Jul 15, 2026

Affected

3 pkgs

Patched

1 / 3

Exploits

None indexed

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

Real-World Exposure

3 pkgs affected

🐹github.com/codeclysm/extract/v3🐹github.com/codeclysm/extract/v4🐹github.com/codeclysm/extract

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

Extract is aA Go library to extract archives in zip, tar.gz or tar.bz2 formats. A maliciously crafted archive may allow an attacker to create a symlink outside the extraction target directory. This vulnerability is fixed in 4.0.0. If you're using the Extractor.FS interface, then upgrading to /v4 will require to implement the new methods that have been added.

Affected Packages

3 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/codeclysm/extract/v3`	all versions	No fix
🐹Go	`github.com/codeclysm/extract/v4`	all versions	4.0.0
🐹Go	`github.com/codeclysm/extract`	all versions	No fix

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/codeclysm/extract/v3. 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
No patched version of github.com/codeclysm/extract/v3 has shipped for CVE-2024-47877 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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 CVE-2024-47877 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 CVE-2024-47877. 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 CVE-2024-47877 in your dependencies?

O3 detects CVE-2024-47877 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