CVE record · CVE-2026-35500

Stack-based buffer overflow in Intel(R) Slim Bootloader

CVSS 8.6 HighEPSS 0.0016 · 5th percentile

Published by the CVE Program (CNA: intel) at 10 Nov 2026, 17:44 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

Affected products, as the CNA wrote them
VendorProductVersions
Not given Intel(R) Slim Bootloader
  • affected See references
Other versions: unaffected
Identifiers
CVE-2026-35500
CNA
intel
Weakness (CWE)
CWE-121
Published
10 Nov 2026
Updated
16 Nov 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

A stack-based buffer overflow in the UEFI firmware of Intel(R) Slim Bootloader may allow privilege escalation within Ring 0 on Bare Metal OS. The record says an unauthenticated user could potentially exploit it with a low-complexity attack and no user interaction, possibly via physical access, with high impact to confidentiality, integrity and availability. No affected versions or fix are listed, and no fix is listed.

Written 19 Nov 2026.

Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.6 High 4.0 CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H CNA (intel)
  • CISA KEV Not listed.
  • EPSS 0.0016, the 5th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 10 Nov 2026, 17:44 UTC Confirmed by the CVE List
  2. 10 Nov 2026, 17:52 UTC First seen by agentprime
  3. 10 Nov 2026, 18:17 UTC Confirmed by NVD

Sources

References from the CNA

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.