CVE-2026-68083

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-10. a secondary CVSS source baseline 9.1; sources differ by 0.0.

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

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

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

ksmbd: fix path resolution in ksmbd_vfs_kern_path_create

The SMB2 open lookup is rooted at the share with LOOKUP_BENEATH, but the create/mkdir/hardlink sink is not: ksmbd_vfs_kern_path_create() builds an absolute path with convert_to_unix_name() and resolves it from AT_FDCWD via start_creating_path(), so a ".." component is walked from the real filesystem root and escapes the export.

An authenticated client races a missing path component so the rooted open lookup returns -ENOENT (taking the create branch) while the same component is present (a directory) when the create walk runs; the create then resolves ".." out of the share.

Root the create walk at the share like the lookup and rename paths already are: resolve the parent with vfs_path_parent_lookup(..., LOOKUP_BENEATH, &share_conf->vfs_path) and create the final component with start_creating_noperm(). convert_to_unix_name() then has no callers and is removed.

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
46(Track)
EG Risk 46/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
Severity91% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

ksmbd: fix path resolution in ksmbd_vfs_kern_path_create - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c8951963d8ed357f70f59e0ad4ddce2199d2016
generic

ksmbd: fix path resolution in ksmbd_vfs_kern_path_create - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98185b3025beeae92d1fe700d5db26b9ac4bf025
generic

ksmbd: fix path resolution in ksmbd_vfs_kern_path_create - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: fix path resolution in ksmbd_vfs_kern_path_create - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/489d1ded01425c0fb33418172c0e4e588467526b

Vendor Advisories for CVE-2026-68083(2)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-68083?
CVE-2026-68083 is a critical vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix path resolution in ksmbdvfskernpathcreate The SMB2 open lookup is rooted at the share with LOOKUP_BENEATH, but the create/mkdir/hardlink sink is not: ksmbdvfskernpathcreate() builds an absolute path with…
When was CVE-2026-68083 disclosed?
CVE-2026-68083 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68083 actively exploited?
CVE-2026-68083 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 62.7% of all scored CVEs.
What is the CVSS score of CVE-2026-68083?
CVE-2026-68083 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-68083?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68083, 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-68083

Explore →

Is Your Infrastructure Affected by CVE-2026-68083?

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