How severe is GHSA-2h46-9x5w-4wf7?

No CVSS score has been assigned to GHSA-2h46-9x5w-4wf7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2h46-9x5w-4wf7?

GHSA-2h46-9x5w-4wf7 affects the following packages: github.com/entireio/cli (Go). Ecosystems affected: Go.

How do I fix GHSA-2h46-9x5w-4wf7?

Update github.com/entireio/cli to 0.7.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2h46-9x5w-4wf7 is resolved across your whole dependency graph.

How do I detect GHSA-2h46-9x5w-4wf7 in my Go dependencies?

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

How do I mitigate GHSA-2h46-9x5w-4wf7 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-2h46-9x5w-4wf7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2h46-9x5w-4wf7 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-2h46-9x5w-4wf7?

GHSA-2h46-9x5w-4wf7 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th 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-2h46-9x5w-4wf7?

GHSA-2h46-9x5w-4wf7 is classified as Path Traversal (CWE-22), CWE-73 (CWE-73). 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-2h46-9x5w-4wf7 published, and has it been updated?

GHSA-2h46-9x5w-4wf7 was published on June 19, 2026 and was last updated on October 24, 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

Entire CLI: Path traversal in checkpoint session metadata allows arbitrary file write during resume/rewindGHSA-2h46-9x5w-4wf7

Fix: entireio/cli#1365

GHSA-2h46-9x5w-4wf7 is a Path Traversal vulnerability in github.com/entireio/cli. A fix is available for github.com/entireio/cli — see the affected versions and patch details below.

Also known asCVE-2026-57208GO-2026-5063

Published

Jun 19, 2026

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 1, 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-2h46-9x5w-4wf7.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs32th percentile — riskier than 32% 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/entireio/cli

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

Impact

A path traversal vulnerability in Entire CLI allows an attacker with push access to the checkpoints repository to craft malicious checkpoint metadata that causes entire session resume or entire checkpoint rewind to write attacker-controlled transcript data outside of the expected session directory.

The issue occurs because checkpoint metadata is fetched from the remote entire/checkpoints/v1 branch and the SessionID field was used to construct filesystem paths without validation in the restore path. A malicious SessionID containing absolute paths or path traversal sequences could cause arbitrary files on the victim’s machine to be overwritten.

Patches

The patched versions (v0.7.7 or v0.7.8-nightly.*) observe stronger input validation and enforce traversal-resistant primitives to ensure that only descending directories can be accessed by the affected commands.

Workarounds

If upgrading immediately is not possible:

Do not run entire session resume or entire checkpoint rewind on repositories where untrusted users can push to entire/checkpoints/v1.
Restrict push access to shared repositories until all collaborators have upgraded.
Inspect the entire/checkpoints/v1 branch for suspicious checkpoint metadata before resuming or rewinding.
Remove or protect shell initialization files and other sensitive user-writable files where feasible.

These mitigations reduce exposure but do not fully address the vulnerability. Upgrading is recommended.

Credits

Thanks Navtej Kathuria for privately reporting this issue to the Entire Security team.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/entireio/cli`	all versions	0.7.7`go get github.com/entireio/cli@v0.7.7`

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/entireio/cli, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/entireio/cli to 0.7.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2h46-9x5w-4wf7 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

### Impact A path traversal vulnerability in Entire CLI allows an attacker with push access to the checkpoints repository to craft malicious checkpoint metadata that causes `entire session resume` or `entire checkpoint rewind` to write attacker-controlled transcript data outside of the expected session directory. The issue occurs because checkpoint metadata is fetched from the remote `entire/checkpoints/v1` branch and the `SessionID` field was used to construct filesystem paths without validation in the restore path. A malicious `SessionID` containing absolute paths or path traversal sequenc

O3 Security · Impact-Aware SCA

Is GHSA-2h46-9x5w-4wf7 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works