CVE-2026-68431

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 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: validate minimum PDU size for transform requests

The receive path applies the minimum SMB2 PDU size check only when ProtocolId is SMB2_PROTO_NUMBER. A packet carrying SMB2_TRANSFORM_PROTO_NUM bypasses the check even when the negotiated dialect does not provide transform handling.

On an SMB 2.1 connection, a short transform packet therefore reaches init_smb2_rsp_hdr(), which interprets the request as a full SMB2 header and reads beyond the request allocation. The copied fields can then be returned to the unauthenticated client.

Compression transforms are converted to ordinary SMB2 messages before protocol validation. After that conversion, validate ordinary SMB2 requests against SMB2_MIN_SUPPORTED_PDU_SIZE and require encryption transform requests to contain both a transform header and an SMB2 header. This rejects truncated requests before work allocation.

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
19%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 17, 2026

Advisory Details (2)

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

ksmbd: validate minimum PDU size for transform requests - kernel/git/stable/linux.git - Linux kernel stable tree

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

ksmbd: validate minimum PDU size for transform requests - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b62c510f59803f82f9b4c76ead2a56833b2984c7

Vendor Advisories for CVE-2026-68431(1)

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

Frequently asked(5)

What is CVE-2026-68431?
CVE-2026-68431 is a critical vulnerability published on August 12, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: validate minimum PDU size for transform requests The receive path applies the minimum SMB2 PDU size check only when ProtocolId is SMB2PROTONUMBER. A packet carrying SMB2TRANSFORMPROTO_NUM bypasses the check even when the…
When was CVE-2026-68431 disclosed?
CVE-2026-68431 was first published in the National Vulnerability Database on August 12, 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-68431 actively exploited?
CVE-2026-68431 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 81.4% of all scored CVEs.
What is the CVSS score of CVE-2026-68431?
CVE-2026-68431 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-68431?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68431, 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-68431

Explore →

Is Your Infrastructure Affected by CVE-2026-68431?

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