CVE-2026-50249 · Infrastructure
NO FIX YET
Intel server boards D50DNP and M50FCP have an out-of-bounds read in GenerationSetup inside their Ring 0 UEFI firmware. A privileged local user can exploit it with high complexity to read confidential data.
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.
Only Intel Server Board D50DNP and M50FCP systems running the affected UEFI firmware are in scope. The attacker needs local, privileged access and a high-complexity setup, so systems without untrusted local users are lower risk. The sources do not give affected firmware versions or a fix.
Not affected if no-local-privileged-users, other-server-boards
Who cares d50dnp, firmware, intel, m50fcp, server-board, uefi
Unknown from the sources.
No fix yet, per the sources.
Out-of-bounds read in the GenerationSetup for the Intel(R) Server Board D50DNP and Intel(R) Server Board M50FCP within Ring 0 UEFI may allow an information disclosure. Startup code and smm adversary with a privileged user combined with a high complexity attack may enable data exposure. 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 (none) and availability (none) 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:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/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.