{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 0.7.6"
      },
      "package": {
        "ecosystem": "Go",
        "name": "github.com/entireio/cli"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.7.7"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [
      "CWE-22",
      "CWE-73"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-06-19T15:00:01Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "### Impact\n\nA 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.\n\nThe 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\u2019s machine to be overwritten.\n\n### Patches\n\nThe 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. \n\n### Workarounds\nIf upgrading immediately is not possible:\n\n- Do not run `entire session resume` or `entire checkpoint rewind` on repositories where untrusted users can push to `entire/checkpoints/v1`.\n- Restrict push access to shared repositories until all collaborators have upgraded.\n- Inspect the `entire/checkpoints/v1` branch for suspicious checkpoint metadata before resuming or rewinding.\n- Remove or protect shell initialization files and other sensitive user-writable files where feasible.\n\nThese mitigations reduce exposure but do not fully address the vulnerability. Upgrading is recommended.\n\n### Credits\nThanks Navtej Kathuria for privately reporting this issue to the Entire Security team.",
  "id": "GHSA-2h46-9x5w-4wf7",
  "modified": "2026-06-19T15:00:01Z",
  "published": "2026-06-19T15:00:01Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/entireio/cli/security/advisories/GHSA-2h46-9x5w-4wf7"
    },
    {
      "type": "WEB",
      "url": "https://github.com/entireio/cli/pull/1365"
    },
    {
      "type": "WEB",
      "url": "https://github.com/entireio/cli/pull/1449"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/entireio/cli"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "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",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Entire CLI: Path traversal in checkpoint session metadata allows arbitrary file write during resume/rewind"
}