dbcve.org
Openshift Container PlatformApplication · Redhat

CVE-2026-1933

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to 4.2.2 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A flaw in Samba's SMB-layer allows authenticated users with underlying filesystem write permissions to create or delete NTFS-style reparse point metadata on shares configured with 'read only = yes', bypassing the intended read-only restriction. This can enable modification of SMB-visible file behavior, including converting regular files into symbolic links or other reparse point types.

MitigationApply Samba security updates when available and review share configurations to ensure proper access controls are enforced at the SMB layer for reparse point operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Openshift Container PlatformApplication
Affected:= 4.0
Enterprise LinuxOperating system
Affected:= 7.0= 8.0= 9.0= 10.0
SambaApplication
Affected:>= 4.1.0, < 4.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Samba version
    Run 'smbd --version' or 'rpm -q samba' to determine the Samba version installed on the system
    Affected if The installed version is >= 4.1.0 and < 4.2.2
  2. Locate Samba share configurations with read-only restriction
    Review smb.conf files (typically in /etc/samba/smb.conf) and identify shares configured with 'read only = yes' or 'readonly = yes'
    Affected if There are shares configured with read only = yes that expose filesystem paths where users have underlying write permissions
  3. Verify underlying filesystem permissions on share paths
    Check filesystem permissions on the directory paths used by read-only shares using 'ls -la' and verify which authenticated users have write access to those directories
    Affected if Authenticated users have write permissions to directories underlying read-only SMB shares, enabling them to create or delete reparse point metadata
  4. Detect existing reparse points on share paths
    Use 'getfattr -d -m . <filename>' or 'fsutil reparsepoint query <filename>' on files within the share paths to check for NTFS reparse point metadata
    Affected if Reparse points exist on files within read-only shares, indicating potential exploitation of this vulnerability

A system is affected if Samba version 4.1.0 through 4.2.1 is in use and there are SMB shares configured as read-only where authenticated users have underlying filesystem write access to create or manipulate reparse points.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.2.2 or later
Fixed in 4.2.2
Interim mitigation

Apply Samba security updates when available and review share configurations to ensure proper access controls are enforced at the SMB layer for reparse point operations.

Recommended fix High confidence

Samba 4.2.2 or later (or the latest available samba package in your distribution's security repositories)

  1. Identify the Samba version currently installed using: rpm -qa | grep samba or smbd --version
  2. For RHEL/CentOS systems: Run 'yum update samba' or 'dnf update samba' to apply available security updates
  3. For RHEL 7.x systems: Upgrade to samba-4.2.2 or later from the Red Hat Enterprise Linux repositories
  4. For RHEL 8.x/9.x systems: Ensure samba-4.2.2 or later is installed via 'dnf install samba' after updating
  5. Restart SMB services after upgrade: 'systemctl restart smb' or 'systemctl restart smbd'
  6. Verify the fixed version is running: 'smbd --version'
Caveat Verify compatibility with existing Samba configurations and dependent services before restarting SMB daemon; minor configuration syntax changes may exist between 4.1.x and 4.2.x

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openshift Container Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1933 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1933 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data