<?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>Cve-2026-1933 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2026-1933/</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>Wed, 27 May 2026 14:19:21 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2026-1933/feed.xml" rel="self" type="application/rss+xml"/><item><title>Samba NTFS Reparse Point Vulnerability (CVE-2026-1933)</title><link>https://feed.craftedsignal.io/briefs/2026-05-samba-ntfs-reparse-point-flaw/</link><pubDate>Wed, 27 May 2026 14:19:21 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-samba-ntfs-reparse-point-flaw/</guid><description>CVE-2026-1933 describes a vulnerability in Samba's handling of NTFS-style reparse points on read-only shares, allowing authenticated users with filesystem write permissions to modify reparse point metadata and potentially alter SMB-visible file behavior.</description><content:encoded><![CDATA[<p>CVE-2026-1933 identifies a flaw in Samba&rsquo;s handling of NTFS-style reparse points. Specifically, on Samba shares configured with <code>read only = yes</code>, a missing SMB-layer access check allows authenticated users who possess underlying filesystem write permissions to manipulate reparse point metadata. This vulnerability enables such users to create or delete reparse points, even on exports that are intended to be read-only. The vulnerability was published on 2026-05-27 and affects Samba implementations utilizing NTFS-style reparse points. This can lead to unauthorized modification of file behavior visible over SMB, including the conversion of files into symbolic links or other reparse point types, potentially disrupting file access and integrity.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker authenticates to a Samba share configured with <code>read only = yes</code>.</li>
<li>Attacker identifies a file or directory suitable for reparse point manipulation.</li>
<li>Attacker uses SMB protocols to send a request to create a new NTFS-style reparse point or modify an existing one.</li>
<li>Samba server receives the SMB request and processes it.</li>
<li>Due to missing SMB-layer access checks, the request bypasses the read-only restriction if the user has underlying filesystem write permissions.</li>
<li>Samba modifies the reparse point metadata on the underlying filesystem.</li>
<li>The target file or directory&rsquo;s behavior is altered, potentially becoming a symbolic link or another reparse point type.</li>
<li>Subsequent SMB clients accessing the modified file or directory now encounter the altered behavior dictated by the reparse point, potentially leading to unauthorized access or denial-of-service conditions.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-1933 allows an authenticated attacker to modify the behavior of files and directories within a Samba share, even if the share is configured as read-only. This can lead to data corruption, unauthorized access, or denial-of-service. While the specific number of affected installations is unknown, any organization using Samba with read-only shares and NTFS-style reparse points may be vulnerable. The impact can range from minor inconvenience to significant disruption of file services, depending on the types of files and directories affected.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply the appropriate patches or updates provided by Samba to address CVE-2026-1933 as soon as they are available.</li>
<li>Review Samba share configurations to ensure that users with write access to the underlying filesystem are appropriately restricted at the SMB layer.</li>
<li>Monitor Samba logs for suspicious activity related to reparse point creation or modification.</li>
<li>Deploy the Sigma rule <code>Detect Samba Reparse Point Manipulation on Read-Only Shares</code> to detect potential exploitation attempts.</li>
<li>Implement file integrity monitoring on critical Samba shares to detect unauthorized changes to file metadata.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>cve</category><category>cve-2026-1933</category><category>samba</category><category>reparse point</category><category>privilege escalation</category><category>smb</category></item></channel></rss>