CVE-2026-1933: Samba: missing access check on reparse point operations
A flaw was found in Samba’s handling of NTFS-style reparse points on shares configured with read only = yes. Due to missing SMB-layer access checks, authenticated users with underlying filesystem write permissions may create or delete reparse point metadata through SMB operations even on read-only exports. This could allow modification of SMB-visible file behavior, including converting files into symbolic links or other reparse point types.
Security readout for executives and security teams
Plain-English summary
CVE-2026-1933 lets authenticated users bypass the intended read-only behavior of some Samba shares when they still have write permission on the underlying filesystem. They may alter reparse point metadata, changing how files appear or behave over SMB. The main business risk is integrity and availability impact on shared file services.
Executive priority
Treat as high priority for enterprise file-sharing environments, especially where read-only shares protect operational, software, or shared business data. Patch during the next urgent maintenance window and reduce filesystem write access immediately where feasible.
Technical view
Samba does not consistently enforce SMB-layer access checks for NTFS-style reparse point create/delete operations on shares configured with read only = yes. If an authenticated user has filesystem write permissions underneath the export, SMB operations may still modify reparse metadata, including symbolic link-like behavior.
Likely exposure
Most relevant exposure is Samba on affected Red Hat Enterprise Linux 7, 8, 9, 10 variants and Red Hat OpenShift Container Platform 4.19 RHCOS where read-only SMB shares map to paths writable by authenticated users.
Exploitation context
The bundle reports no KEV listing and provides no evidence of active exploitation. Abuse requires authentication and underlying filesystem write permission, but network access and low attack complexity make this important for shared file servers.
Researcher notes
The key condition is the mismatch between Samba share read-only policy and underlying filesystem write rights. CVSS is 7.1 with integrity and availability impact. Evidence is Red Hat-focused; the bundle does not establish exploit availability or broader non-Red Hat impact.
Mitigation direction
Apply the applicable Red Hat security advisory updates for affected Samba or RHCOS packages.
Review vendor guidance for fixed package versions and platform-specific remediation steps.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.