CVE-2026-99083

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-108934 (ENISA EUVD) · GHSA-2j87-48p3-j5xw (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ksmbd: fix heap out-of-bounds write in krb5_authenticate()

In krb5_authenticate(), out_len is calculated to determine available headroom in response_buf for the incoming Kerberos AP-REP token. However, when SMB2_SESSION_SETUP is processed as a non-first element of a compounded SMB2 request, the calculation omits work->next_smb2_rsp_hdr_off.

This causes out_len to overstate remaining buffer headroom by the cumulative size of prior responses in the compound chain. Consequently, the length check in ksmbd_krb5_authenticate() (*out_len <= resp->spnego_blob_len) passes erroneously, allowing memcpy() to write the AP-REP blob past the end of response_buf into adjacent kernel heap memory.

Fix this by subtracting work->next_smb2_rsp_hdr_off when computing out_len, ensuring it accurately reflects physical remaining buffer space.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
38th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 23, 2026

Last Modified

October 30, 2026

Advisory Details (5)

Auto-updated Oct 24, 2026
Patch available.
Web page

ksmbd: fix heap out-of-bounds write in krb5_authenticate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/80af1bde97d5a85ad6f2c40ca894ccc8fa75a27a
Web page

ksmbd: fix heap out-of-bounds write in krb5_authenticate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/59c6dcc5dd9dafe764ca0d40525933b2be69b059
Web page

ksmbd: fix heap out-of-bounds write in krb5_authenticate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/517404e157395d0f8da125ca956c566895dfcd06
Web page

ksmbd: fix heap out-of-bounds write in krb5_authenticate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4722d06b2907585074252061b1024a696c1cfc23
Web page

ksmbd: fix heap out-of-bounds write in krb5_authenticate() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23a0be6a84a38ac169eeab49017934e8e27c65f0

Vendor Advisories for CVE-2026-99083(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 13× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  2. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  3. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  6. 2026-10-30 13:29 UTCEG score recompute
  7. 2026-10-30 13:29 UTCVendor advisory
  8. 2026-10-30 13:29 UTCGHSA enrichmentGHSA-2j87-48p3-j5xw · GitHub severity HIGH · GitHub CVSS 8.8
  9. 2026-10-30 12:50 UTCEG score recompute
  10. 2026-10-30 12:50 UTCVendor advisory
  11. 2026-10-30 12:50 UTCGHSA enrichmentGHSA-2j87-48p3-j5xw · GitHub severity HIGH · GitHub CVSS 8.8
  12. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  13. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  14. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-10-26 07:26 UTCEG score recompute
  17. 2026-10-26 07:26 UTCGHSA enrichmentGHSA-2j87-48p3-j5xw · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-10-26 07:11 UTCEG score recompute
  19. 2026-10-26 07:11 UTCGHSA enrichmentGHSA-2j87-48p3-j5xw · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-10-25 13:46 UTCEG score recompute
  22. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-10-24 14:27 UTCEG score recompute
  24. 2026-10-24 14:27 UTCGHSA enrichmentGHSA-2j87-48p3-j5xw
  25. 2026-10-24 14:15 UTCEG score recomputeFirst assessed: 8.8 HIGH
Show 5 more
  1. 2026-10-24 14:14 UTCGHSA enrichmentGHSA-2j87-48p3-j5xw
  2. 2026-10-24 14:13 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  3. 2026-10-23 13:26 UTCNVD update
  4. 2026-10-23 13:00 UTCEG score recompute
  5. 2026-10-23 12:59 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-99083?
CVE-2026-99083 is a high-severity vulnerability; its CVE record was published on October 23, 2026. In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix heap out-of-bounds write in krb5_authenticate() In krb5_authenticate(), out_len is calculated to determine available headroom in response_buf for the incoming Kerberos AP-REP token. However, when SMB2_SESSION_SETUP is…
When was the CVE record for CVE-2026-99083 published?
The CVE record for CVE-2026-99083 was published on October 23, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-99083 actively exploited?
CVE-2026-99083 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-99083?
CVE-2026-99083 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-99083?
A fix for CVE-2026-99083 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-99083 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-99083

Explore →

Is Your Infrastructure Affected by CVE-2026-99083?

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