CVE-2026-28746 · Infrastructure
NO FIX YET
Intel Slim Bootloader has an out-of-bounds read in its AuthenticateComponent code, which runs in Ring 0 on bare-metal OS setups. A privileged local user can trigger it to cause a denial of service, with no confidentiality or integrity impact stated.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
The sources describe a local attack by a privileged system-software adversary against Intel Slim Bootloader in a bare-metal OS setting. Systems that do not run Slim Bootloader are not affected. The sources do not say which versions are affected or which configurations are exposed.
Not affected if no-slim-bootloader
Who cares bare-metal, intel, slim-bootloader
Unknown from the sources.
No fix yet, per the sources.
Out-of-bounds read in the AuthenticateComponent for the Intel(R) Slim Bootloader within Ring 0: Bare Metal OS may allow a denial of service. System software adversary with a privileged user combined with a low complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.