Loading vulnerability…
CVE-2026-1933 is an improper access-control vulnerability in Samba reparse-point operations introduced with reparse-point support in Samba 4.21. Samba failed to enforce SMB share-level and read-only-handle access checks before setting or deleting NTFS-style reparse-point metadata. Consequently, an authenticated user who has write permission in the underlying filesystem can modify reparse-point metadata through SMB despite accessing an export configured with "read only = yes" or using a read-only file handle. Affected releases include Samba 4.21.x, 4.22.x through 4.22.9, 4.23.x through 4.23.7, and 4.24.x through 4.24.2.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
21 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Samba vulnerability caused by a missing access check on reparse point operations.
A Samba vulnerability caused by a missing access check on reparse point operations.
A Samba vulnerability caused by a missing access check on reparse point operations.
A Samba vulnerability caused by a missing access check on reparse point operations.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.