Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-111045 Overview
CVE-2026-111045 is a symlink-based path traversal vulnerability in CLI Bridge, a tool that provides filesystem access within a workspace root. Versions prior to 0.0.2 fail to properly validate dangling symbolic links during write operations. An attacker who can place a symlink in the workspace can cause the write_file operation to follow the link and write arbitrary files outside the intended workspace boundary. The flaw is tracked as CWE-59: Improper Link Resolution Before File Access and is fixed in version 0.0.2.
Critical Impact
Attackers can write arbitrary files outside the workspace root by exploiting dangling symlinks, enabling tampering with configuration files, scripts, or sensitive application data.
Affected Products
- CLI Bridge versions prior to 0.0.2
- Workspaces using the vulnerable resolveSafePath function
- Integrations relying on CLI Bridge for sandboxed filesystem access
Discovery Timeline
- 2026-10-19 - CVE-2026-111045 published to NVD
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-111045
Vulnerability Analysis
CLI Bridge enforces workspace isolation through a resolveSafePath function that normalizes and verifies filesystem paths before write operations. The function relies on fs.realpathSync to resolve symbolic links against the real filesystem. When the target of a symlink does not exist, fs.realpathSync throws an ENOENT error, triggering a fallback code path. The fallback only resolves the parent directory of the requested path and then returns the original symlink path as safe.
This fallback behavior allows a dangling symlink inside the workspace to point to an arbitrary absolute location outside the workspace root. When write_file subsequently opens the path for writing, the operating system follows the symlink and creates the target file at the attacker-controlled location. The result is a write primitive that escapes the workspace boundary without triggering the safety check.
Root Cause
The root cause is improper link resolution before file access [CWE-59]. The resolveSafePath function treats a failed real-path resolution as a benign condition rather than a validation failure. By resolving only the parent directory, the function loses visibility into the final symlink target. The check validates where the symlink lives, not where it points.
Attack Vector
An attacker with the ability to place a symlink in the workspace creates a link whose target is a nonexistent path outside the workspace, for example /etc/cron.d/evil. The attacker then requests a write_file operation against the symlink path. fs.realpathSync throws ENOENT, the fallback approves the path, and the write proceeds to the attacker-chosen location. The attack requires no authentication and can be triggered over the network.
# Patch excerpt from v0.0.2 (.gitignore additions for test harness)
.cli-bridge-audit.log
PROJECT_LOG.md
+
+# Scratch & test scripts
+scratch/
+test*.js
+test*.mjs
Source: GitHub commit 284a84c — the commit hardens resolveSafePath against dangling symlink escape and adds scratch directories to version control exclusions. Full fix details are available in GitHub Security Advisory GHSA-8jc4-x8v7-2q9r.
Detection Methods for CVE-2026-111045
Indicators of Compromise
- Symbolic links inside CLI Bridge workspace directories whose targets resolve to paths outside the workspace root.
- Unexpected file creation or modification in system directories such as /etc, user home directories, or application configuration paths.
- Entries in .cli-bridge-audit.log showing write_file operations against paths that resolve differently than their declared workspace location.
Detection Strategies
- Audit workspace directories for symlinks using find <workspace> -type l and verify each target resides within the workspace root.
- Monitor CLI Bridge audit logs for write_file operations that produce ENOENT fallback traces in older versions.
- Correlate process-level file writes from the CLI Bridge binary with their resolved on-disk destinations to flag out-of-scope writes.
Monitoring Recommendations
- Enable filesystem auditing (auditd on Linux, FSEvents on macOS) on paths outside expected workspaces where CLI Bridge should never write.
- Alert on creation of symlinks within workspaces by non-interactive processes.
- Track installed CLI Bridge versions across hosts to confirm all deployments are at 0.0.2 or later.
How to Mitigate CVE-2026-111045
Immediate Actions Required
- Upgrade CLI Bridge to version 0.0.2 or later on all systems where it is installed.
- Inventory existing workspaces and remove any symbolic links whose targets fall outside the workspace root.
- Restrict which users and automation agents can submit write_file requests to CLI Bridge until patching is complete.
Patch Information
The fix is included in CLI Bridge release v0.0.2 and merged through Pull Request #3. The patch hardens resolveSafePath so that an ENOENT from fs.realpathSync no longer short-circuits validation, ensuring the final resolved path is verified against the workspace root even when the target does not yet exist.
Workarounds
- Run CLI Bridge under a dedicated low-privilege account whose write permissions are limited to the workspace directory.
- Mount workspace directories with the nosymfollow option where supported, or disallow symlink creation inside workspaces.
- Place CLI Bridge inside a container or chroot that cannot reach sensitive host paths.
# Upgrade CLI Bridge to the patched release
npm install cli-bridge@0.0.2
# Audit a workspace for symlinks pointing outside the root
find /path/to/workspace -type l -exec sh -c 'readlink -f "$1" | grep -qv "^/path/to/workspace" && echo "ESCAPE: $1"' _ {} \;
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

