CVE-2026-1933

HIGHNVD 6.57.1
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. NVD baseline CVSS 6.5; sources differ by 0.6.

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

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
56%
KEV
Not listed

Published

May 27, 2026

Last Modified

August 27, 2026

Advisory Details (5)

Auto-updated Jun 13, 2026
Patch available. Sources: redhat.
generic

15992 – (CVE-2026-1933) CVE-2026-1933 [SECURITY] Missing access check on reparse point operations

https://bugzilla.samba.org/show_bug.cgi?id=15992
redhat Patch Available

2447317 – (CVE-2026-1933) CVE-2026-1933 samba: Missing access check on reparse point operations

Affected: Red Hat Enterprise Linux 10

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

cve-details

https://access.redhat.com/security/cve/CVE-2026-1933
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:25049
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:22963

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuwinbind (2:4.22.3+dfsg-4ubuntu2.4) @ questing2026-08-27ubuntu
redhatrhcos-418.94.202608142238-02026-08-26redhat
redhatrhcos-4.20.9.6.202608121719-02026-08-18redhat
redhatrhcos-4.22.9.8.202608130832-02026-08-18redhat
redhatrhcos-4.21.9.6.202608122143-02026-08-18redhat
redhatrhcos-4.19.9.6.202606241344-02026-07-02redhat
redhatsamba-0:4.19.4-105.el9_4.42026-06-23redhat
redhatsamba-0:4.21.3-114.el10_0.12026-06-23redhat
redhatsamba-0:4.15.5-16.el8_6.12026-06-23redhat
redhatsamba-0:4.17.5-7.el8_8.12026-06-23redhat
redhatsamba-0:4.17.5-105.el9_2.52026-06-23redhat
redhatsamba-0:4.21.3-14.el9_6.12026-06-15redhat
redhatsamba-0:4.23.5-10.el9_82026-06-10redhat
redhatsamba-0:4.23.5-109.el10_22026-06-03redhat
redhatsamba-0:4.19.4-16.el8_102026-06-03redhat

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)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
samba4.22.10-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
samba4.23.8-r0
Debian:13(1)
PackageVulnerable rangeFixed inDependents
samba2:4.22.3+dfsg-4 ... 2:4.22.8+dfsg-0+deb13u1 (7 versions)2:4.22.8+dfsg-0+deb13u2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
samba2:4.22.3+dfsg-4 ... 2:4.24.3+dfsg-1~bpo13+1 (30 versions)2:4.24.3+dfsg-1

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 25× in last 7d / 140× 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 355 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-1933?
CVE-2026-1933 is a high vulnerability published on May 27, 2026. 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…
When was CVE-2026-1933 disclosed?
CVE-2026-1933 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-1933 actively exploited?
CVE-2026-1933 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 44.0% of all scored CVEs.
What is the CVSS score of CVE-2026-1933?
CVE-2026-1933 has a CVSS v3 base score of 6.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.1.
How do I remediate CVE-2026-1933?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-1933, 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-1933

Explore →

Is Your Infrastructure Affected by CVE-2026-1933?

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