CVE-2026-59260
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 · uneditedOpenWrt luci-app-samba4 read ACL grants file.exec permission on /usr/sbin/smbd, allowing authenticated delegated users to execute the Samba daemon with caller-controlled command-line arguments. Attackers can pass arbitrary Samba global options such as message command to a root smbd process, triggering command execution when SMB protocol messages are processed.
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 confidenceOpenWrt's luci-app-samba4 has a misconfigured ACL that grants file.exec permission on /usr/sbin/smbd to authenticated delegated users. This allows these users to start the Samba daemon with attacker-controlled command-line arguments, including the dangerous 'message command' global option. When smbd (running as root) processes SMB messages, it executes the attacker-specified commands with root privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 if luci-app-samba4 is installedRun 'opkg list-installed | grep luci-app-samba4' or check /etc/config/luci for samba4 entriesAffected if The package is not installed, this CVE does not apply
-
Verify ACL grants file.exec on /usr/sbin/smbdInspect the luci-app-samba4 ACL configuration file (typically in /etc/luci/authban or /etc/config/luci) for a rule granting file.exec permission to /usr/sbin/smbd for delegated usersAffected if ACL contains file.exec permission on /usr/sbin/smbd for delegated users
-
Check Samba global configuration for message commandInspect /etc/samba/smb.conf or use 'testparm -s' to review the global section for a 'message command' directiveAffected if A 'message command' directive is present in the Samba global configuration
-
Identify delegated users with elevated ACL permissionsReview the luci-app-samba4 user delegation settings in /etc/config/luci or the ACL configuration to see which users are granted delegated accessAffected if There are delegated users configured with permissions that include file.exec on /usr/sbin/smbd
A user is affected if luci-app-samba4 is installed with ACL permissions granting file.exec on /usr/sbin/smbd to delegated users AND the Samba configuration contains a message command directive, allowing privilege escalation via SMB messages.
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 dataRemove or restrict the file.exec permission on /usr/sbin/smbd in the luci-app-samba4 ACL configuration, and disable the 'message command' option in the Samba global configuration to prevent command execution via SMB protocol messages.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-59260 — 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-59260 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