CVE-2026-111045: CLI Bridge: High-severity sandbox escape via dangling symlink
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 writefile follows the link and can write arbitrary files outside the workspace root. This issue is fixed in version 0.0.2.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
CLI Bridgeto a version that resolves this vulnerability.Fixed in 0.0.2
Event History
Frequently Asked Questions
Which deployments are affected?
CLI Bridge versions before 0.0.2 are affected. The issue applies where an attacker can cause a dangling symlink within the workspace root to point to a nonexistent path outside that root.
What does an attacker need to exploit this?
The attacker needs to use a dangling symlink located in the workspace that points outside the workspace root, then invoke write_file on that path. No authentication or user interaction is required according to the supplied vector.
What is the impact of successful exploitation?
Successful exploitation lets write_file follow the symlink and write arbitrary files outside the configured workspace root. The reported impact is integrity loss; no confidentiality or availability impact is indicated.
How can I remediate this issue?
Upgrade CLI Bridge to version 0.0.2 or later, which fixes the unsafe fallback handling when realpathSync encounters ENOENT.