Entire CLI: Path traversal in checkpoint session metadata allows arbitrary file write during resume/rewind

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.2 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:L/VA:N/SC:N/SI:H/SA:H · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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…

Published by the source

19 Jun 2026, 15:00 UTC

Last modified by the source

22 Jun 2026, 18:51 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2h46-9x5w-4wf7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-2h46-9x5w-4wf7

Advisory: Entire CLI: Path traversal in checkpoint session metadata allows arbitrary file write during resume/rewind
IDs: GHSA-2h46-9x5w-4wf7
Record: https://patchnext.com/advisories/ghsa-2h46-9x5w-4wf7 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/entireio/cli 0.7.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/entireio/cli: affected <= 0.7.6; fixed in 0.7.7

## Suggested inspection (read-only)
- Go github.com/entireio/cli: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/entireio/cli.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2h46-9x5w-4wf7 (GitHub-reviewed advisory GHSA-2h46-9x5w-4wf7 lists affected ranges: Go github.com/entireio/cli >=0 <=0.7.6)

Commands are suggestions: review each one before running it.