CVE-2026-15779

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreMEDIUM confidence

Score 6.1 from GitHub Security Advisory published 2026-07-15. a secondary CVSS source baseline 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.1Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
6.1
EG Score
6.1(medium)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity61% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

July 15, 2026

Last Modified

July 15, 2026

Advisory Details (5)

Auto-updated Jul 15, 2026
Patch available. Sources: redhat.
generic

nsswitch/pam_winbind.c · samba-4.24.3 · The Samba Team / Samba · GitLab

https://gitlab.com/samba-team/samba/-/blob/samba-4.24.3/nsswitch/pam_winbind.c#L1590
generic

nsswitch/pam_winbind.c · samba-4.23.5 · The Samba Team / Samba · GitLab

https://gitlab.com/samba-team/samba/-/blob/samba-4.23.5/nsswitch/pam_winbind.c#L1622
generic

nsswitch/pam_winbind.c · samba-4.19.4 · The Samba Team / Samba · GitLab

https://gitlab.com/samba-team/samba/-/blob/samba-4.19.4/nsswitch/pam_winbind.c
redhat Patch Available

2499991 – (CVE-2026-15779) CVE-2026-15779 samba-winbind: samba: pam_winbind mkhomedir chowns critical system paths without validation

https://bugzilla.redhat.com/show_bug.cgi?id=2499991
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-15779

Vendor Advisories for CVE-2026-15779(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuwinbind (2:4.23.6+dfsg-1ubuntu2.2) @ resolute2026-09-18ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
samba2:4.13.13+dfsg-1 ... 2:4.24.5+dfsg-1~bpo13+1 (245 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
samba2:4.17.10+dfsg-0+deb12u1 ... 2:4.25.0~rc1+dfsg-1 (175 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
samba2:4.22.10+dfsg-0+deb13u1 ... 2:4.25.0~rc1+dfsg-1 (43 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
samba2:4.22.3+dfsg-4 ... 2:4.25.0~rc1+dfsg-1 (37 versions)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 63× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 160 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-18 04:46 UTCEG score recompute
  3. 2026-09-18 04:46 UTCVendor advisory
  4. 2026-09-18 04:46 UTCGHSA enrichment
  5. 2026-09-16 14:07 UTCEPSS rescore
  6. 2026-09-14 07:08 UTCEG score recompute
  7. 2026-09-14 07:08 UTCVendor advisory
  8. 2026-09-14 07:08 UTCGHSA enrichment
  9. 2026-09-13 16:46 UTCEPSS rescore
  10. 2026-09-13 07:16 UTCEG score recompute
  11. 2026-09-13 07:16 UTCVendor advisory
  12. 2026-09-13 07:16 UTCGHSA enrichment
  13. 2026-09-12 15:00 UTCEPSS rescore
  14. 2026-09-11 21:47 UTCEG score recompute
  15. 2026-09-11 21:47 UTCVendor advisory
  16. 2026-09-11 21:47 UTCGHSA enrichment
  17. 2026-09-11 14:52 UTCEPSS rescore
  18. 2026-09-11 09:36 UTCEPSS rescore
  19. 2026-09-10 09:34 UTCEPSS rescore
  20. 2026-09-08 22:00 UTCEPSS rescore
  21. 2026-09-08 00:57 UTCEG score recompute
  22. 2026-09-08 00:57 UTCVendor advisory
  23. 2026-09-08 00:56 UTCGHSA enrichment
  24. 2026-09-06 13:47 UTCEPSS rescore
  25. 2026-09-05 20:52 UTCEG score recompute
Show 75 more
  1. 2026-09-05 20:52 UTCVendor advisory
  2. 2026-09-05 20:51 UTCGHSA enrichment
  3. 2026-09-04 05:06 UTCEPSS rescore
  4. 2026-09-01 04:39 UTCEPSS rescore
  5. 2026-08-31 03:58 UTCEG score recompute
  6. 2026-08-31 03:58 UTCVendor advisory
  7. 2026-08-31 03:58 UTCGHSA enrichment
  8. 2026-08-30 19:17 UTCEPSS rescore
  9. 2026-08-30 03:54 UTCEG score recompute
  10. 2026-08-30 03:54 UTCVendor advisory
  11. 2026-08-30 03:54 UTCGHSA enrichment
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-28 21:41 UTCEPSS rescore
  14. 2026-08-27 23:54 UTCEG score recompute
  15. 2026-08-27 23:54 UTCVendor advisory
  16. 2026-08-27 23:54 UTCGHSA enrichment
  17. 2026-08-27 14:25 UTCEPSS rescore
  18. 2026-08-26 23:48 UTCEG score recompute
  19. 2026-08-26 23:48 UTCVendor advisory
  20. 2026-08-26 23:48 UTCGHSA enrichment
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 23:55 UTCEG score recompute
  23. 2026-08-25 23:55 UTCVendor advisory
  24. 2026-08-25 23:55 UTCGHSA enrichment
  25. 2026-08-25 13:48 UTCEPSS rescore
  26. 2026-08-24 23:37 UTCEG score recompute
  27. 2026-08-24 23:37 UTCVendor advisory
  28. 2026-08-24 23:37 UTCGHSA enrichment
  29. 2026-08-23 23:44 UTCEG score recompute
  30. 2026-08-23 23:44 UTCVendor advisory
  31. 2026-08-23 23:44 UTCGHSA enrichment
  32. 2026-08-23 00:19 UTCEPSS rescore
  33. 2026-08-22 23:53 UTCVendor advisory
  34. 2026-08-22 23:53 UTCGHSA enrichment
  35. 2026-08-22 00:01 UTCEG score recompute
  36. 2026-08-22 00:01 UTCVendor advisory
  37. 2026-08-22 00:01 UTCGHSA enrichment
  38. 2026-08-21 23:49 UTCEPSS rescore
  39. 2026-08-21 00:09 UTCEG score recompute
  40. 2026-08-21 00:09 UTCVendor advisory
  41. 2026-08-21 00:09 UTCGHSA enrichment
  42. 2026-08-20 22:55 UTCEPSS rescore
  43. 2026-08-20 00:17 UTCEG score recompute
  44. 2026-08-20 00:17 UTCVendor advisory
  45. 2026-08-20 00:17 UTCGHSA enrichment
  46. 2026-08-19 17:03 UTCEPSS rescore
  47. 2026-08-18 20:00 UTCEG score recompute
  48. 2026-08-18 20:00 UTCVendor advisory
  49. 2026-08-18 20:00 UTCGHSA enrichment
  50. 2026-08-17 13:47 UTCEPSS rescore
  51. 2026-08-17 13:29 UTCEG score recompute
  52. 2026-08-17 13:29 UTCVendor advisory
  53. 2026-08-17 13:29 UTCGHSA enrichment
  54. 2026-08-16 14:56 UTCEPSS rescore
  55. 2026-08-16 13:37 UTCEG score recompute
  56. 2026-08-16 13:37 UTCVendor advisory
  57. 2026-08-16 13:37 UTCGHSA enrichment
  58. 2026-08-16 02:14 UTCEPSS rescore
  59. 2026-08-15 13:45 UTCEG score recompute
  60. 2026-08-15 13:45 UTCVendor advisory
  61. 2026-08-15 13:45 UTCGHSA enrichment
  62. 2026-08-15 01:30 UTCEPSS rescore
  63. 2026-08-14 13:53 UTCEG score recompute
  64. 2026-08-14 13:53 UTCVendor advisory
  65. 2026-08-14 13:53 UTCGHSA enrichment
  66. 2026-08-13 22:00 UTCEPSS rescore
  67. 2026-08-13 14:01 UTCVendor advisory
  68. 2026-08-13 14:01 UTCGHSA enrichment
  69. 2026-08-12 14:08 UTCEG score recompute
  70. 2026-08-12 14:08 UTCVendor advisory
  71. 2026-08-12 14:08 UTCGHSA enrichment
  72. 2026-08-12 13:50 UTCEPSS rescore
  73. 2026-08-11 14:15 UTCEG score recompute
  74. 2026-08-11 14:15 UTCVendor advisory
  75. 2026-08-11 14:15 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-15779?
CVE-2026-15779 is a medium vulnerability published on July 15, 2026. A flaw was found in samba's pamwinbind. When mkhomedir is enabled, pamwinbind 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…
When was CVE-2026-15779 disclosed?
CVE-2026-15779 was first published in the National Vulnerability Database on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15779 actively exploited?
CVE-2026-15779 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.8% of all scored CVEs.
What is the CVSS score of CVE-2026-15779?
CVE-2026-15779 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-15779?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15779, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-15779

Explore →

Is Your Infrastructure Affected by CVE-2026-15779?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.