CVE-2026-43377

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-08. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.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: 8.1Exploit: None knownExposed: 0

A fix is available — apply it.

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

ksmbd: Don't log keys in SMB3 signing and encryption key generation

When KSMBD_DEBUG_AUTH logging is enabled, generate_smb3signingkey() and generate_smb3encryptionkey() log the session, signing, encryption, and decryption key bytes. Remove the logs to avoid exposing credentials.

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

Published

May 8, 2026

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

ksmbd: Don't log keys in SMB3 signing and encryption key generation - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: Don't log keys in SMB3 signing and encryption key generation - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: Don't log keys in SMB3 signing and encryption key generation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/441336115df26b966575de56daf7107ed474faed
generic

ksmbd: Don't log keys in SMB3 signing and encryption key generation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4084ed720d7d5f4e975c9e4a6267a552dad3b24a
generic

ksmbd: Don't log keys in SMB3 signing and encryption key generation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/407cc37c21d51f9b9d4d20204b04890880cfa6ae
generic

ksmbd: Don't log keys in SMB3 signing and encryption key generation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3fe2d9ec166b7df9a8df6c0fdcfc210572e27e3f

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-23ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-23ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
linuxKernel @ 6.1.167—osv

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (122 versions)6.19.10-1—

All Vendor Advisories

(14)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43377?
CVE-2026-43377 is a high vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: Don't log keys in SMB3 signing and encryption key generation When KSMBDDEBUGAUTH logging is enabled, generate_smb3signingkey() and generate_smb3encryptionkey() log the session, signing, encryption, and decryption key bytes.…
When was CVE-2026-43377 disclosed?
CVE-2026-43377 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43377 actively exploited?
CVE-2026-43377 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 83.8% of all scored CVEs.
What is the CVSS score of CVE-2026-43377?
CVE-2026-43377 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-43377?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43377, 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-43377

Explore →

Is Your Infrastructure Affected by CVE-2026-43377?

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

Start Free Scan →Browse All CVEs