Out-of-bounds write in the XmlCliCommonDxe for the Intel(R) Server Board D50DNP and Intel(R) Server Board M50FCP within Ring 0 UEFI may…
Affects Intel Server Board D50DNP and M50FCP running UEFI before R01.02.0006. Intel recommends updating to UEFI R01.02.0006 or later, which fixes the issue.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in R01.02.0006
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Intel Server Board D50DNP or M50FCP running UEFI before R01.02.0006 A high complexity attack, with attack requirements present
- 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? →
- 14/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
Out-of-bounds write in the XmlCliCommonDxe for the Intel(R) Server Board D50DNP and Intel(R) Server Board M50FCP within Ring 0 UEFI may allow an escalation of privilege. Startup code and smm adversary with a privileged user combined with a high complexity attack may enable local code execution. This result may potentially occur via local access when attack requirements are 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 Server Board D50DNP or M50FCP firmware before UEFI R01.02.0006
Read the source excerpt
“Intel® Server Board D50DNP and M50FCP UEFI before version R01.02.0006.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Intel Server Board D50DNP or M50FCP running UEFI before R01.02.0006 A high complexity attack, with attack requirements presentUpgrade to a fixed version: R01.02.0006.
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-57882 (Out-of-bounds write in the XmlCliCommonDxe for the Intel(R) Server Board D50DNP and Intel(R) Server Board M50FCP within Ring 0 UEFI may…), 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-57882 (entry last updated 2026-11-10): Affected: - n/a Intel(R) Server Board D50DNP and Intel(R) Server Board M50FCP: version range not reported Fixed versions: R01.02.0006. Conditions (all must be true for the bug to be hit): - Intel Server Board D50DNP or M50FCP running UEFI before R01.02.0006 (source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01554.html) - A high complexity attack, with attack requirements present (source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01554.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-57882 is not listed as of cve.now's last read. This KEV status is for CVE-2026-57882 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-01554.html - https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01554.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-57882 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-57882.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- n/a Intel(R) Server Board D50DNP and Intel(R) Server Board M50FCP
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-57882
Is CVE-2026-57882 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?
An out-of-bounds write in the XmlCliCommonDxe component of the board's Ring 0 UEFI firmware may allow an escalation of privilege through local code execution. The attack is rated high complexity because attack requirements must be present.Source: intel.com
Am I affected, and how do I check?
Intel Server Board D50DNP and Intel Server Board M50FCP with UEFI firmware before version R01.02.0006. To check, compare the installed UEFI version against R01.02.0006.Source: intel.com
How do I fix CVE-2026-57882?
Intel recommends updating Intel Server Board D50DNP and M50FCP to UEFI version R01.02.0006 or later.Source: intel.com