Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 271/271 feeds/APIs · 464/464 docs · 7/9 advisories · checked 15:21 UTC Customize Public modeDiscuss ChangeIntel on Discord
Advisory catalogGHSA-2h46-9x5w-4wf7

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

Exact source revision recorded 24 Oct 2026 13:19:41 UTC. It does not establish the source's current position. Latest evidence.

osv · GHSA-2h46-9x5w-4wf7

Published

### 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.

Source published
19 Jun 2026 15:00:01 UTC
Source modified
24 Oct 2026 02:55:48 UTC
Observed here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS_V4 · 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

Publisher rating · MODERATE

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 24 Oct 15:21 UTC · 271 of 271 readable · 269 fully read · documentation 464/464 current