Live › vulnerability › CVE-2026-111045
Go to dashboardCLI Bridge checks file paths against the workspace root, but a dangling symlink pointing outside the workspace passes that check when its target does not exist. A write_file call then follows the link and can create or overwrite arbitrary files outside the workspace.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Teams running CLI Bridge versions before 0.0.2 where an agent or user can make write_file calls inside a workspace root and can create symlinks there. Exposure depends on the write path being reachable; the sources do not say how the bridge is exposed to callers.
No product ranges from the sources yet.
npm ls cli-bridge (package name unknown; confirm in the project's lockfile)find <workspace> -type l -exec ls -l {} +0.0.2 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
CLI Bridge provides filesystem access within a workspace root. Prior to 0.0.2, a dangling symlink pointing outside the workspace root bypasses resolveSafePath when fs.realpathSync throws ENOENT for a nonexistent target. The fallback resolves only the parent directory and returns the symlink path as safe, so write_file follows the link and can write arbitrary files outside the workspace root. This issue is fixed in version 0.0.2.
This page as .md · .json · in your agent: get_signal("CVE-2026-111045")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.