CLI Bridge allows a sandbox escape when a dangling symbolic link points outside the workspace root. The resolver fails when fs.realpathSync throws ENOENT for a missing target; it then incorrectly treats the parent directory of the symlink as safe, permitting write_file to write to arbitrary filesystem paths. Based on the description, it is inferred that the vulnerability is a path‑traversal weakness (CWE‑59) that can lead to unintended modifications or creation of sensitive files beyond the sandbox.

The vulnerability affects the anshupriyan:cli-bridge product. All releases prior to 0.0.2 are impacted; the fix was introduced in 0.0.2 so any deployment using an earlier version is susceptible.

The CVSS score of 7.5 indicates high severity, although the EPSS score is not available and it is not yet listed in the CISA KEV catalog. Based on the description, it is inferred that the likely attack vector is an attacker creating a dangling symlink within the workspace that points outside the intended sandbox. Attackers can exploit the flaw by supplying the crafted symlink path; they require access to the CLI or the ability to create files within the workspace, but no elevated privileges are needed once the symlink is accepted. Overall, the risk is high for environments where users can write input to the workspace.