Vulnerability in samba (UBUNTU-CVE-2026-15779)

Summary

Vulnerability in samba (UBUNTU-CVE-2026-15779). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2:4.15.13+dfsg-0ubuntu1.13 or later.

Original description

The description as published by the source.

A flaw was found in samba's pam_winbind. When mkhomedir is enabled, pam_winbind chowns the target account's home directory without validating the path is not a critical system directory such as /. On affected systems, accounts with / as their home directory (a common default for system accounts) can have this triggered not only by root, but by a non-root user holding a narrow sudo delegation to run commands as that account, causing ownership of / to change and resulting in severe denial of service (SSH, sudo, and package-manager failures). The change does not grant write access to / (which ships with restrictive 0555 permissions on RHEL), so the impact is availability loss rather than further privilege escalation.

Source: OSV.dev (Open Source Vulnerabilities) OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as UBUNTU-CVE-2026-15779 has been found in samba.
Risk of unauthorized operations or information disclosure.
What to do: upgrade samba to 2:4.15.13+dfsg-0ubuntu1.13 or later.
If unsure, ask your IT team or search "samba UBUNTU-CVE-2026-15779" on the vendor's site.

UBUNTU-CVE-2026-15779 (samba)
Attack vector: local / no user interaction
Patched: 2:4.15.13+dfsg-0ubuntu1.13 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in samba.

📍 Affected scope

Check the vendor advisory for the affected versions of samba.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2:4.15.13+dfsg-0ubuntu1.13.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'samba' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'samba' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で samba を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade samba to 2:4.15.13+dfsg-0ubuntu1.13
```
ステージング環境で 2:4.15.13+dfsg-0ubuntu1.13 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:14.04:LTS samba

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:Pro:16.04:LTS samba

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:Pro:18.04:LTS samba

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:Pro:20.04:LTS samba

[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]

Ubuntu:22.04:LTS samba

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:4.15.13+dfsg-0ubuntu1.13"}]}]

Ubuntu:24.04:LTS samba

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:4.19.5+dfsg-4ubuntu9.7"}]}]

Ubuntu:26.04:LTS samba

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2:4.23.6+dfsg-1ubuntu2.2"}]}]

References

advisory ubuntu.com
report ubuntu.com
report cve.org