Openshift Container PlatformApplication · Redhat
CVE-2026-2340
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 · uneditedA flaw was found in Samba’s vfs_worm module. The module is intended to provide write-once, read-many (WORM) protections by preventing modification of files after a configurable grace period. Due to insufficient validation during rename operations, an authenticated user with write access to a share could overwrite a protected file by renaming a newly created file over the existing WORM-protected file.
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 · high confidenceThe vfs_worm module in Samba provides write-once, read-many protections intended to prevent file modification after a configurable grace period. However, insufficient validation during rename operations allows an authenticated user with write access to bypass these protections by creating a new file and renaming it over an existing WORM-protected file, effectively overwriting the protected content.
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
= 4.0
Enterprise LinuxOperating system
= 7.0= 8.0= 9.0= 10.0>= 4.1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Samba versionRun 'smbd --version' or 'rpm -q samba' to determine the Samba version installedAffected if Version is greater than or equal to 4.1.0 and matches Red Hat Enterprise Linux 7.0, 8.0, 9.0, or 10.0, or Red Hat OpenShift Container Platform 4.0
-
Locate Samba configuration fileFind smb.conf typically in /etc/samba/smb.conf or /etc/smb.confAffected if Configuration file exists and Samba is in use
-
Verify vfs_worm module is loadedSearch the smb.conf file for 'vfs objects = worm' or 'vfs_worm' entries in any share definitions or in the [global] sectionAffected if The vfs_worm module is explicitly configured and loaded for one or more shares
-
Check share write and rename permissionsReview each share using vfs_worm and examine 'write list', 'read only', 'create mask', and 'force user' settings. Test rename operations (mv/ren) from a client with write access to a WORM-protected shareAffected if Shares with vfs_worm enabled allow write access AND rename operations are not explicitly restricted
Your environment is affected if you run Samba >= 4.1.0 with the vfs_worm module loaded on shares that permit both write and rename operations, allowing an authenticated user to overwrite WORM-protected files via rename.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataRestrict or disable write and rename permissions on shares using vfs_worm until a vendor patch is available. Consider implementing additional file system-level ACLs to block rename operations on protected files.
Fix this in Openshift Container Platform
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2340 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2340 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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