CVE-2026-35500: Intel(R) Slim Bootloader (high)

Summary

Stack-based buffer overflow in the UEFI firmware for the Intel(R) Slim Bootloader within Ring 0: Bare Metal OS may allow an escalation of privilege. Startup code and smm adversary with an unauthenticated user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via physical access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (high) and availability (high) impacts.

Who should check

Teams running Intel Slim Bootloader firmware on listed Intel Core, Xeon, Pentium, Celeron, Atom and N-series processor platforms

Read the source excerpt

“Stack-based buffer overflow in the UEFI firmware for the Intel® Slim Bootloader”

intel.com

cve.now Index

19Pcve.now Index 19 of 100 · methodology v3 · provisional

Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
Exposure5/25Specific setups only
Reach?/20Unknown. No tracked technology or package matched
Severity8.6/10CVSS 8.6
No patch5/5No patch listed yet

What would change the score

Would score about 69 if added to CISA KEV
Would score about 64 if CISA's SSVC rates exploitation active
Would score about 29 if CISA's SSVC rates it automatable

How the score works · Rankings

What to do

Check whether your setup matches what the bug needs.
Intel Slim Bootloader UEFI firmware on the affected Intel processor platforms
Workaround: The checked facts include no workaround. Check Intel's advisory for any mitigation guidance for the affected platform until a firmware update is available.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-35500 (Stack-based buffer overflow in the UEFI firmware for the Intel(R) Slim Bootloader within Ring 0: Bare Metal OS may allow an escalation of…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-35500 (entry last updated 2026-11-10):
Affected:
- n/a Intel(R) Slim Bootloader: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Intel Slim Bootloader UEFI firmware on the affected Intel processor platforms (source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01526.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: physical access, no login, no user action.
CISA KEV: CVE-2026-35500 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-35500 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01526.html
- https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01526.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Entry: https://cve.now/CVE-2026-35500
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-35500.

Timeline

Nov 10, 2026, 5:44 PM UTCCVE published
Nov 10, 2026, 6:26 PM UTCFirst seen by cve.now

Affected versions

n/a Intel(R) Slim Bootloader
Version range not reported

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

Link
intel.com · content/www/us/en/security-center/advisory/intel-sa-01526.html

CVE record · 2

Establishes: The identifier and description.

Record
CVE List · CVE-2026-35500
Record
NVD · CVE-2026-35500

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-35500

Is CVE-2026-35500 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A stack-based buffer overflow in the UEFI firmware of Intel Slim Bootloader may allow an escalation of privilege to Ring 0 on the affected system.Source: intel.com

Am I affected, and how do I check?

The checked facts cover Intel Slim Bootloader UEFI firmware on affected Intel processor platforms but list no specific versions. Compare your firmware build against the platform list in Intel's advisory.Source: intel.com

How do I fix CVE-2026-35500?

The checked facts name no fixed version, so no specific upgrade target can be given. Follow Intel's advisory for firmware updates for the affected platform.Source: intel.com

What if there's no patch?

The checked facts include no workaround. Check Intel's advisory for any mitigation guidance for the affected platform until a firmware update is available.Source: intel.com

Stack-based buffer overflow in the UEFI firmware for the Intel(R) Slim Bootloader within Ring 0: Bare Metal OS may allow an escalation of…