CVE-2026-1933

MEDIUMNVD 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
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 6.5Exploit: NoneExposed: 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
54.8%
KEV
Not listed

Published

May 27, 2026

Last Modified

July 15, 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(11)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuwinbind (2:4.15.13+dfsg-0ubuntu1.12) @ jammy2026-07-12ubuntu
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.

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 13× in last 7d / 71× 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 197 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-1933?
CVE-2026-1933 is a medium 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 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-1933 actively exploited?
CVE-2026-1933 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 54.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.