<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>CLI Bridge - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/cli-bridge/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Mon, 19 Oct 2026 18:09:47 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/cli-bridge/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>Arbitrary File Write in CLI Bridge via Dangling Symlink Traversal</title><link>https://feed.craftedsignal.io/briefs/2026-10-cli-bridge-path-traversal/</link><pubDate>Mon, 19 Oct 2026 18:09:47 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-10-cli-bridge-path-traversal/</guid><description>CLI Bridge versions prior to 0.0.2 are vulnerable to path traversal through improper symlink resolution, potentially allowing arbitrary file writes outside the intended workspace root.</description><content:encoded><![CDATA[<p>CLI Bridge contains a critical path traversal vulnerability (CVE-2026-111045) that impacts filesystem security within the workspace root. The issue arises in the <code>resolveSafePath</code> function, which fails to properly validate paths when encountering a dangling symlink (a symlink pointing to a nonexistent target). Specifically, when <code>fs.realpathSync</code> throws an <code>ENOENT</code> exception, the logic incorrectly falls back to resolving only the parent directory and marks the symlink path as safe. Because the <code>write_file</code> operation subsequently follows these symlinks, an attacker can manipulate symlinks to write files to arbitrary locations outside the defined workspace boundary. This vulnerability is addressed in version 0.0.2.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows an attacker to bypass workspace isolation, leading to arbitrary file write operations. This can be leveraged to overwrite critical system configuration files, inject malicious code into application directories, or gain unauthorized persistent access to the underlying host system, depending on the permissions of the process running CLI Bridge.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Update CLI Bridge to version 0.0.2 or later immediately to incorporate the patch for CVE-2026-111045.</li>
<li>Audit filesystem access logs to identify attempts to write files outside of designated workspace directories.</li>
<li>Monitor for the creation of symbolic links within workspace environments that point to sensitive system directories or files.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>path-traversal</category><category>arbitrary-file-write</category><category>cve</category></item></channel></rss>