GHSA-2h46-9x5w-4wf7 — cli
Fix: entireio/cli#1365GHSA-2h46-9x5w-4wf7 is a security vulnerability in github.com/entireio/cli. A fix is available for github.com/entireio/cli — see the affected versions and patch details below.
Entire CLI: Path traversal in checkpoint session metadata allows arbitrary file write during resume/rewind
Real-World Exposure
github.com/entireio/cliReal-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 resumeorentire checkpoint rewindon repositories where untrusted users can push toentire/checkpoints/v1. - Restrict push access to shared repositories until all collaborators have upgraded.
- Inspect the
entire/checkpoints/v1branch 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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/entireio/cli | all versions | 0.7.7go get github.com/entireio/cli@v0.7.7 |
Detection & mitigation playbook
Open-source dependencyDetect
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
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2h46-9x5w-4wf7 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2h46-9x5w-4wf7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2h46-9x5w-4wf7 in your dependencies?
O3 Security finds GHSA-2h46-9x5w-4wf7 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.