CVE-2026-93282

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-24. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.1Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: fix maximum allowed access checks

The DACL permission check looks for an ACE matching the current user and falls back to the Everyone ACE. It does not consider an Authenticated Users ACE, even though an authenticated session is a member of that well-known group.

As a result, opening a file whose access is granted through S-1-5-11 can incorrectly fail with STATUS_ACCESS_DENIED. Treat an Authenticated Users ACE as a fallback entry alongside Everyone.

The maximal access calculation also combines access masks from every ACE, regardless of whether its SID applies to the current user. This can grant rights belonging to an unrelated principal. Process only ACEs applying to the user, Everyone, or Authenticated Users, and accumulate allowed and denied masks in ACL order. Preserve explicitly requested access bits so they are validated against the resulting maximal mask.

When ACCESS_SYSTEM_SECURITY is denied, report STATUS_PRIVILEGE_NOT_HELD instead of the generic STATUS_ACCESS_DENIED. Access to the system ACL requires a security privilege that ksmbd does not grant.

For regular files, include FILE_EXECUTE in maximal access when the client requested GENERIC_EXECUTE and the DACL grants the complete file-read set. Keep a direct FILE_EXECUTE request subject to the explicit DACL bit. This matches the POSIX file ACL mapping without broadening specific execute requests.

Do not replace rights from an applicable NT ACE with a POSIX ACL entry. The POSIX ACL is only a fallback when no user, Everyone, or Authenticated Users ACE applies; otherwise it can incorrectly broaden the stored DACL.

This fixes smb2.maximum_allowed.maximum_allowed.

CVSS v3
8.1
EG Score
8.1HIGHhigh confidence
EG Risk
41
EG Risk 41/100CISA SSVC

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
Severity81% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 24, 2026

Last Modified

September 25, 2026

Advisory Details (2)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

ksmbd: fix maximum allowed access checks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cc2f133e80eb2c4a04bfa77a2f207749fe2f516a
generic

ksmbd: fix maximum allowed access checks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/35d5c59fe6b1d9fe43fb14eb384f69ee1a120f9c

Vendor Advisories for CVE-2026-93282(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (355 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (176 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 38× in last 7d / 58× 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.

  1. 2026-10-05 00:13 UTCEG score recompute
  2. 2026-10-05 00:13 UTCVendor advisory
  3. 2026-10-05 00:13 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 11:36 UTCVendor advisory
  6. 2026-10-04 11:36 UTCGHSA enrichment
  7. 2026-10-03 23:00 UTCEG score recompute
  8. 2026-10-03 23:00 UTCVendor advisory
  9. 2026-10-03 23:00 UTCGHSA enrichment
  10. 2026-10-03 10:24 UTCVendor advisory
  11. 2026-10-03 10:24 UTCGHSA enrichment
  12. 2026-10-02 21:49 UTCEG score recompute
  13. 2026-10-02 21:49 UTCVendor advisory
  14. 2026-10-02 21:49 UTCGHSA enrichment
  15. 2026-10-02 09:13 UTCVendor advisory
  16. 2026-10-02 09:13 UTCGHSA enrichment
  17. 2026-10-01 20:38 UTCEG score recompute
  18. 2026-10-01 20:38 UTCVendor advisory
  19. 2026-10-01 20:38 UTCGHSA enrichment
  20. 2026-10-01 19:51 UTCEPSS rescore
  21. 2026-10-01 08:01 UTCVendor advisory
  22. 2026-10-01 08:01 UTCGHSA enrichment
  23. 2026-09-30 19:25 UTCEG score recompute
  24. 2026-09-30 19:25 UTCGHSA enrichment
  25. 2026-09-30 15:04 UTCEPSS rescore
Show 33 more
  1. 2026-09-30 06:50 UTCVendor advisory
  2. 2026-09-30 06:50 UTCGHSA enrichment
  3. 2026-09-29 18:15 UTCEG score recompute
  4. 2026-09-29 18:15 UTCVendor advisory
  5. 2026-09-29 18:15 UTCGHSA enrichment
  6. 2026-09-29 05:38 UTCEG score recompute
  7. 2026-09-29 05:38 UTCVendor advisory
  8. 2026-09-29 05:38 UTCGHSA enrichment
  9. 2026-09-28 17:02 UTCEG score recompute
  10. 2026-09-28 17:02 UTCVendor advisory
  11. 2026-09-28 17:02 UTCGHSA enrichment
  12. 2026-09-28 13:52 UTCEPSS rescore
  13. 2026-09-28 13:52 UTCEPSS rescore
  14. 2026-09-28 04:23 UTCGHSA enrichment
  15. 2026-09-27 15:47 UTCEG score recompute
  16. 2026-09-27 15:47 UTCGHSA enrichment
  17. 2026-09-27 13:49 UTCEPSS rescore
  18. 2026-09-27 03:12 UTCEG score recompute
  19. 2026-09-27 03:12 UTCGHSA enrichment
  20. 2026-09-26 15:59 UTCEPSS rescore
  21. 2026-09-26 14:36 UTCGHSA enrichment
  22. 2026-09-26 02:01 UTCEG score recompute
  23. 2026-09-26 02:01 UTCGHSA enrichment
  24. 2026-09-25 13:24 UTCEG score recompute
  25. 2026-09-25 13:24 UTCGHSA enrichment
  26. 2026-09-25 12:57 UTCEG score recompute
  27. 2026-09-25 12:57 UTCGHSA enrichment
  28. 2026-09-25 05:18 UTCEG score recompute▲ 8.10
  29. 2026-09-25 05:18 UTCGHSA enrichment
  30. 2026-09-25 05:16 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  31. 2026-09-24 16:30 UTCNVD update
  32. 2026-09-24 15:57 UTCEG score recompute
  33. 2026-09-24 15:56 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93282?
CVE-2026-93282 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix maximum allowed access checks The DACL permission check looks for an ACE matching the current user and falls back to the Everyone ACE. It does not consider an Authenticated Users ACE, even though an authenticated session…
When was CVE-2026-93282 disclosed?
CVE-2026-93282 was first published on September 24, 2026, with the most recent update on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93282 actively exploited?
CVE-2026-93282 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93282?
CVE-2026-93282 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93282?
No fix for CVE-2026-93282 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-93282 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-93282?

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

Book a Demo →Browse All CVEs