Untrusted pointer dereference in the FirmwareWakingVector for the Intel(R) Slim Bootloader within Ring 0: Bare Metal OS may allow an…
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Intel Slim Bootloader, with the bug in the FirmwareWakingVector, running under a Ring 0 bare metal OS
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 18/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Untrusted pointer dereference in the FirmwareWakingVector for the Intel(R) Slim Bootloader within Ring 0: Bare Metal OS may allow an escalation of privilege. System software adversary with a privileged user combined with a low complexity attack may enable escalation of privilege. 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 (high), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
Who should check
Teams running or shipping Intel Slim Bootloader firmware on Intel processors with a Ring 0 bare metal OS
Read the source excerpt
“Potential security vulnerabilities in the Intel® Slim Bootloader may allow denial of service or escalation of privilege.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.4/10CVSS 8.4
- No patch5/5No patch listed yet
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 28 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Intel Slim Bootloader, with the bug in the FirmwareWakingVector, running under a Ring 0 bare metal OSWorkaround: The available facts do not list a workaround. Until a fix is available, follow Intel's advisory guidance and limit local privileged access to the affected system.
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-50175 (Untrusted pointer dereference in the FirmwareWakingVector for the Intel(R) Slim Bootloader within Ring 0: Bare Metal OS may allow an…), 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-50175 (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, with the bug in the FirmwareWakingVector, running under a Ring 0 bare metal OS (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: local access, high-privilege login, no user action. CISA KEV: CVE-2026-50175 is not listed as of cve.now's last read. This KEV status is for CVE-2026-50175 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-50175 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-50175.
Timeline
- CVE published
- First 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
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-50175
Is CVE-2026-50175 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?
The bug is an untrusted pointer dereference in the FirmwareWakingVector of Intel Slim Bootloader. The advisory says it may allow an escalation of privilege by an attacker who already has privileged local access.Source: intel.com
Am I affected, and how do I check?
The advisory covers Intel Slim Bootloader with the bug in the FirmwareWakingVector, running under a Ring 0 bare metal OS. No affected version range is given in the available facts, so check the bootloader build and OS setup against Intel's advisory.Source: intel.com
How do I fix CVE-2026-50175?
No fixed version is given in the available facts. Check Intel's advisory for a patched Slim Bootloader release and apply it when it is available.Source: intel.com
What if there's no patch?
The available facts do not list a workaround. Until a fix is available, follow Intel's advisory guidance and limit local privileged access to the affected system.Source: intel.com