CVE-2026-93801

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.0EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.0Exploit: 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:

smb/client: zero-initialize stack-allocated cifs_open_info_data

Stack-allocated cifs_open_info_data may contain random data. This can make some fields have wrong value if they are not set later.

CVSS v3
7.0
EG Score
7.0HIGHhigh confidence
EG Risk
36
EG Risk 36/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
Severity70% × 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.1%
EPSS %ILE
1st
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 (3)

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

smb/client: zero-initialize stack-allocated cifs_open_info_data - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8fce4cf4369c766a3293a05419500cbfde72e60d
generic

smb/client: zero-initialize stack-allocated cifs_open_info_data - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/74ff47e6c4213fcfeba2de448d9cbda200507d22
generic

smb/client: zero-initialize stack-allocated cifs_open_info_data - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/22532dd88694ed20bdd47523ffa709f166ce776b

Vendor Advisories for CVE-2026-93801(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
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 44× in last 7d / 66× 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 05:37 UTCEG score recompute
  2. 2026-10-05 05:37 UTCVendor advisory
  3. 2026-10-05 05:37 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 18:35 UTCVendor advisory
  6. 2026-10-04 18:34 UTCGHSA enrichment
  7. 2026-10-04 07:31 UTCVendor advisory
  8. 2026-10-04 07:31 UTCGHSA enrichment
  9. 2026-10-03 20:29 UTCEG score recompute
  10. 2026-10-03 20:29 UTCVendor advisory
  11. 2026-10-03 20:29 UTCGHSA enrichment
  12. 2026-10-03 14:26 UTCEPSS rescore
  13. 2026-10-03 09:26 UTCVendor advisory
  14. 2026-10-03 09:26 UTCGHSA enrichment
  15. 2026-10-02 22:24 UTCEG score recompute
  16. 2026-10-02 22:24 UTCVendor advisory
  17. 2026-10-02 22:24 UTCGHSA enrichment
  18. 2026-10-02 11:21 UTCVendor advisory
  19. 2026-10-02 11:21 UTCGHSA enrichment
  20. 2026-10-02 00:17 UTCEG score recompute
  21. 2026-10-02 00:17 UTCVendor advisory
  22. 2026-10-02 00:17 UTCGHSA enrichment
  23. 2026-10-01 19:51 UTCEPSS rescore
  24. 2026-10-01 13:15 UTCVendor advisory
  25. 2026-10-01 13:15 UTCGHSA enrichment
Show 41 more
  1. 2026-10-01 02:13 UTCVendor advisory
  2. 2026-10-01 02:13 UTCGHSA enrichment
  3. 2026-09-30 15:11 UTCEG score recompute
  4. 2026-09-30 15:11 UTCVendor advisory
  5. 2026-09-30 15:11 UTCGHSA enrichment
  6. 2026-09-30 15:04 UTCEPSS rescore
  7. 2026-09-30 04:08 UTCVendor advisory
  8. 2026-09-30 04:08 UTCGHSA enrichment
  9. 2026-09-29 17:02 UTCEG score recompute
  10. 2026-09-29 17:02 UTCVendor advisory
  11. 2026-09-29 17:02 UTCGHSA enrichment
  12. 2026-09-29 06:00 UTCEG score recompute
  13. 2026-09-29 06:00 UTCVendor advisory
  14. 2026-09-29 06:00 UTCGHSA enrichment
  15. 2026-09-28 18:58 UTCEG score recompute
  16. 2026-09-28 18:58 UTCVendor advisory
  17. 2026-09-28 18:58 UTCGHSA enrichment
  18. 2026-09-28 13:52 UTCEPSS rescore
  19. 2026-09-28 13:52 UTCEPSS rescore
  20. 2026-09-28 07:55 UTCVendor advisory
  21. 2026-09-28 07:55 UTCGHSA enrichment
  22. 2026-09-27 20:53 UTCEG score recompute
  23. 2026-09-27 20:53 UTCGHSA enrichment
  24. 2026-09-27 13:49 UTCEPSS rescore
  25. 2026-09-27 09:50 UTCGHSA enrichment
  26. 2026-09-26 22:48 UTCEG score recompute
  27. 2026-09-26 22:48 UTCGHSA enrichment
  28. 2026-09-26 15:59 UTCEPSS rescore
  29. 2026-09-26 11:46 UTCGHSA enrichment
  30. 2026-09-26 00:44 UTCEG score recompute
  31. 2026-09-26 00:44 UTCGHSA enrichment
  32. 2026-09-25 13:23 UTCEG score recompute
  33. 2026-09-25 13:23 UTCGHSA enrichment
  34. 2026-09-25 12:56 UTCEG score recompute
  35. 2026-09-25 12:56 UTCGHSA enrichment
  36. 2026-09-25 05:17 UTCEG score recompute▲ 7.00
  37. 2026-09-25 05:17 UTCGHSA enrichment
  38. 2026-09-25 05:16 UTCMITRE cvelistV5CVSS v3 → 7 · severity → HIGH
  39. 2026-09-24 17:33 UTCNVD update
  40. 2026-09-24 16:30 UTCEG score recompute
  41. 2026-09-24 16:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93801?
CVE-2026-93801 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: smb/client: zero-initialize stack-allocated cifsopeninfo_data Stack-allocated cifsopeninfo_data may contain random data. This can make some fields have wrong value if they are not set later.
When was CVE-2026-93801 disclosed?
CVE-2026-93801 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-93801 actively exploited?
CVE-2026-93801 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93801?
CVE-2026-93801 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93801?
No fix for CVE-2026-93801 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-93801 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-93801

Explore →

Is Your Infrastructure Affected by CVE-2026-93801?

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

Book a Demo →Browse All CVEs