<?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/"><channel><title>Directory-Traversal — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/directory-traversal/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 29 Apr 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/directory-traversal/feed.xml" rel="self" type="application/rss+xml"/><item><title>OpenClaw Arbitrary Directory Deletion Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-04-openclaw-directory-deletion/</link><pubDate>Wed, 29 Apr 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-openclaw-directory-deletion/</guid><description>OpenClaw before 2026.4.2 is vulnerable to arbitrary directory deletion in mirror mode, enabling attackers to delete remote directories by manipulating remoteWorkspaceDir and remoteAgentWorkspaceDir configuration values.</description><content:encoded><![CDATA[<p>OpenClaw before version 2026.4.2 is susceptible to an arbitrary directory deletion vulnerability (CVE-2026-41383) when operating in mirror mode. An attacker with control over the OpenShell configuration paths, specifically <code>remoteWorkspaceDir</code> and <code>remoteAgentWorkspaceDir</code>, can trigger the deletion of unintended remote directory contents. This is achieved by manipulating these configuration values to point to sensitive directories. The subsequent mirror sync operation replaces the deleted contents with data from the attacker&rsquo;s workspace, leading to data loss and potential system compromise. This vulnerability allows an attacker to potentially wipe out important data on the remote end.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker gains access to the OpenClaw configuration.</li>
<li>The attacker modifies the <code>remoteWorkspaceDir</code> and/or <code>remoteAgentWorkspaceDir</code> configuration values to point to a target directory they wish to delete.</li>
<li>The attacker initiates a mirror sync operation.</li>
<li>OpenClaw, using the attacker-controlled path, connects to the remote system.</li>
<li>OpenClaw deletes the contents of the directory specified by the modified <code>remoteWorkspaceDir</code> or <code>remoteAgentWorkspaceDir</code>.</li>
<li>OpenClaw uploads the contents of the attacker&rsquo;s local workspace to the now-empty remote directory, effectively replacing the original data.</li>
<li>The targeted remote directory now contains the attacker&rsquo;s data instead of the original contents.</li>
<li>The attacker achieves arbitrary directory deletion and data replacement, potentially causing significant disruption and data loss.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability can lead to arbitrary deletion of files and directories on the remote system where OpenClaw is used in mirror mode. The impact includes potential data loss, service disruption, and the replacement of legitimate data with attacker-controlled content. Given the CVSS v3.1 score of 8.1, this vulnerability is considered high severity due to the potential for significant data integrity and availability impact.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade OpenClaw to version 2026.4.2 or later to remediate CVE-2026-41383.</li>
<li>Monitor OpenClaw configuration files for unauthorized modifications to <code>remoteWorkspaceDir</code> and <code>remoteAgentWorkspaceDir</code> using a file integrity monitoring system.</li>
<li>Implement strict access controls to OpenClaw configuration files to prevent unauthorized modification of these settings.</li>
<li>Deploy the Sigma rule to detect suspicious process execution related to modification of openclaw configuration files.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cve-2026-41383</category><category>directory-traversal</category><category>file-deletion</category><category>openclaw</category></item><item><title>compressing npm Package Symlink Bypass Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-04-compressing-symlink-bypass/</link><pubDate>Sat, 18 Apr 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-compressing-symlink-bypass/</guid><description>A vulnerability in the `compressing` npm package (&lt;=v2.1.0) allows for arbitrary file overwrite via symlink path traversal, bypassing a previous patch for CVE-2026-24884.</description><content:encoded><![CDATA[<p>The <code>compressing</code> npm package (v2.1.0 and earlier) contains a critical vulnerability that permits arbitrary file overwrites due to a symlink path traversal bypass. This bypass affects the patch for CVE-2026-24884. The vulnerability arises from an incomplete validation in the <code>isPathWithinParent</code> utility, where path string checks are performed without verifying the filesystem state, specifically symbolic links. By cloning a malicious repository containing a pre-existing symbolic link, a victim unknowingly plants a &ldquo;poisoned path&rdquo; on their system. The attacker can then craft a malicious archive that, when extracted by the vulnerable library, follows the symlink and overwrites arbitrary files. The ease of exploitation via <code>git clone</code> makes this vulnerability particularly dangerous.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker creates a malicious Git repository containing a symbolic link (e.g., <code>config_file</code>) pointing to a sensitive target file or directory (e.g., <code>/tmp/fake_root/etc/passwd</code>).</li>
<li>Attacker generates a malicious payload (e.g., <code>payload.tar</code>) containing a file with the same name as the symbolic link (e.g., <code>config_file</code>) and uploads both to their Git repository.</li>
<li>Victim clones the attacker&rsquo;s Git repository using <code>git clone</code>. This action automatically restores the symbolic link on the victim&rsquo;s system.</li>
<li>Victim runs an application that utilizes the vulnerable <code>compressing</code> library to extract the <code>payload.tar</code> archive.</li>
<li>The <code>compressing</code> library&rsquo;s <code>isPathWithinParent</code> function resolves the path to the file being extracted. Due to lack of <code>lstat</code> checks, the symbolic link is not detected.</li>
<li>The <code>fs.writeFile</code> function follows the symlink, writing the contents of the file from <code>payload.tar</code> to the targeted sensitive file (e.g., <code>/tmp/fake_root/etc/passwd</code>).</li>
<li>Arbitrary file overwrite occurs, potentially leading to privilege escalation or code execution.</li>
<li>Attacker achieves persistent access or control by overwriting critical system files.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows attackers to overwrite arbitrary files on the victim&rsquo;s system, potentially leading to privilege escalation by modifying sensitive system files such as <code>/etc/passwd</code>. Remote Code Execution (RCE) can be achieved by overwriting executable binaries or startup scripts. Data corruption can also occur through the modification of application data or database files. This vulnerability impacts developers and organizations using the <code>compressing</code> library up to version v2.1.0 when extracting untrusted archives.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade the <code>compressing</code> npm package to a patched version that includes proper symlink handling. This is the primary remediation.</li>
<li>Inspect Git repositories for suspicious symbolic links before cloning. Use <code>git ls-tree -r &lt;commit-ish&gt; | grep 120000</code> to search for symlinks in a repository.</li>
<li>Implement runtime monitoring for file writes to unexpected locations based on the <code>compressing</code> library&rsquo;s activity. Create a detection rule based on <code>process_creation</code> and <code>file_event</code> to detect writes to sensitive directories such as <code>/etc</code> by processes spawned by Node.js that also load the vulnerable <code>compressing</code> module.</li>
<li>Monitor network connections originating from processes related to the <code>compressing</code> library after file extraction. Create a Sigma rule based on <code>network_connection</code> and <code>process_creation</code> to detect unusual outbound connections after archive extraction.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>npm</category><category>supply-chain</category><category>symlink</category><category>directory-traversal</category><category>privilege-escalation</category><category>arbitrary-file-overwrite</category></item><item><title>LORIS Directory Traversal Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-04-loris-traversal/</link><pubDate>Wed, 08 Apr 2026 19:25:24 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-loris-traversal/</guid><description>LORIS, a neuroimaging research data management web application, is vulnerable to directory traversal (CVE-2026-35446) due to an incorrect order of operations in the FilesDownloadHandler, allowing authenticated attackers to access unauthorized files.</description><content:encoded><![CDATA[<p>LORIS (Longitudinal Online Research and Imaging System) is a self-hosted web application designed for data and project management in neuroimaging research. Versions 24.0.0 up to, but not including, 27.0.3 and 28.0.1 contain a directory traversal vulnerability (CVE-2026-35446) in the FilesDownloadHandler. This flaw stems from an incorrect order of operations, potentially enabling an attacker to escape the intended download directories and access sensitive files. Successful exploitation requires authentication and could lead to unauthorized access to sensitive research data. Users are advised to upgrade to versions 27.0.3 or 28.0.1 to mitigate this vulnerability. This vulnerability impacts organizations utilizing LORIS for managing sensitive neuroimaging data, potentially exposing research data.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker authenticates to the LORIS web application with valid credentials.</li>
<li>The attacker crafts a malicious HTTP request to the <code>FilesDownloadHandler</code>.</li>
<li>The crafted request includes a manipulated file path designed to traverse directories outside the intended download directory.</li>
<li>The <code>FilesDownloadHandler</code> processes the request with an incorrect order of operations when validating the file path.</li>
<li>The application bypasses the intended directory restrictions due to the flawed validation process.</li>
<li>The attacker gains access to files and directories outside of the designated download directory.</li>
<li>The attacker reads sensitive data, including neuroimaging data, project files, or configuration files.</li>
<li>The attacker may exfiltrate sensitive data for malicious purposes, such as espionage or sale on the dark web.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this directory traversal vulnerability (CVE-2026-35446) in LORIS could lead to unauthorized access to sensitive neuroimaging research data. The number of affected organizations is unknown, but any organization using LORIS versions 24.0.0 to before 27.0.3 and 28.0.1 is potentially vulnerable. The impact includes data breaches, intellectual property theft, and potential compromise of patient privacy if patient data is stored within the LORIS system.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade LORIS to version 27.0.3 or 28.0.1 to remediate CVE-2026-35446, as indicated in the overview.</li>
<li>Implement the &ldquo;Detect LORIS Directory Traversal Attempt&rdquo; Sigma rule to monitor for suspicious file download requests.</li>
<li>Review web server access logs for unusual file download patterns or attempts to access files outside the intended download directories using the file_event log source to detect potential exploitation attempts.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>directory-traversal</category><category>web-application</category><category>neuroimaging</category></item><item><title>SiYuan Note Taking Application Directory Traversal Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-03-siyuan-traversal/</link><pubDate>Thu, 26 Mar 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-03-siyuan-traversal/</guid><description>SiYuan note taking application is vulnerable to a directory traversal via the /api/file/readDir endpoint, which does not require authentication, allowing an attacker to enumerate the directory structure and retrieve file names, potentially leading to arbitrary document reading.</description><content:encoded><![CDATA[<p>The SiYuan note-taking application is susceptible to a critical directory traversal vulnerability affecting versions up to 0.0.0-20260317012524-fe4523fff2c8. The vulnerability resides in the <code>/api/file/readDir</code> endpoint, which lacks authentication. This allows unauthenticated attackers to send POST requests to enumerate directories and retrieve file names within the application&rsquo;s data and configuration directories. Successful exploitation allows a malicious actor to gain sensitive information about the application&rsquo;s file structure, and could be chained with a file-reading vulnerability to achieve arbitrary document access. This poses a significant risk to confidentiality and data security.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>An attacker identifies a vulnerable SiYuan instance.</li>
<li>The attacker sends an unauthenticated POST request to the <code>/api/file/readDir</code> endpoint.</li>
<li>The POST request includes a <code>path</code> parameter specifying the directory to list, such as <code>data</code> or <code>conf</code>.</li>
<li>The SiYuan application processes the request without authentication and returns a JSON response containing a list of files and directories within the specified path.</li>
<li>The attacker parses the JSON response to identify interesting files and directories.</li>
<li>The attacker repeats steps 2-5 to traverse deeper into the directory structure.</li>
<li>The attacker identifies the location of sensitive documents or configuration files.</li>
<li>The attacker leverages a separate file reading vulnerability (not detailed in this brief) to access and exfiltrate the identified documents or configuration files, gaining unauthorized access to sensitive information.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this directory traversal vulnerability allows an attacker to enumerate the entire directory structure of a SiYuan notebook. This may expose sensitive information stored within the application&rsquo;s data and configuration files. When combined with a file reading vulnerability, attackers can access and exfiltrate arbitrary documents, potentially leading to data breaches and confidentiality compromise. The number of affected users is potentially large, given the popularity of the SiYuan note-taking application. Targeted sectors would include any organization or individual using SiYuan for storing sensitive information.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply updates to SiYuan to versions greater than 0.0.0-20260317012524-fe4523fff2c8 that patch CVE-2026-33670.</li>
<li>Monitor web server logs for POST requests to the <code>/api/file/readDir</code> endpoint, as detailed in the rule below, and investigate unexpected activity.</li>
<li>Deploy the Sigma rule provided to detect exploitation attempts in web server logs, tuning it for your environment.</li>
<li>Block access from IP address <code>172.18.40.184</code> observed in the exploit PoC, if seen connecting to your SiYuan instances.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>directory-traversal</category><category>siyuan</category><category>cve-2026-33670</category></item></channel></rss>