Severity by source
CVSS:4.0/AV:L/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/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
Local access and high privileges required per attack description; scope change to C reflects SMM escape impacting hypervisor and co-tenant systems beyond OS boundary.
Primary rating from Vendor (intel).
CVSS VectorVendor: intel
Lifecycle Timeline
2DescriptionCVE.org
Improper access control in the firmware for some in Alias Checking Trusted Module for some Intel(R) Xeon(R) processors may allow an escalation of privilege. Startup code and SMM adversary with a privileged user combined with a high 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 (none) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (high) and availability (none) impacts.
AnalysisAI
Privilege escalation in the Alias Checking Trusted Module (ACTM) firmware for certain Intel Xeon processors allows a local privileged attacker to escalate to System Management Mode (SMM) execution, achieving high confidentiality and integrity impact across both the directly compromised system and subsequent systems such as co-hosted hypervisors or tenant workloads. The attack requires high-complexity local technique combined with pre-existing privileged user access, placing it firmly in the advanced persistent threat actor category. No public exploit has been identified at time of analysis, and Intel has published advisory INTEL-SA-01439 to address this firmware flaw.
Technical ContextAI
The Alias Checking Trusted Module (ACTM) is a firmware-level security component in certain Intel Xeon server processors that performs alias checking operations during processor startup sequences. System Management Mode (SMM) is a highly privileged x86/x64 CPU execution context that operates from protected SMRAM memory, invisible to and independent of the operating system and hypervisor - making SMM compromise among the most dangerous firmware-level escalation classes. CWE-284 (Improper Access Control) identifies the root cause: the ACTM firmware fails to enforce proper access boundaries between privilege levels, allowing an attacker with startup code or SMM adversary primitives combined with high OS-level privileges to cross into SMM execution. The CVSS 4.0 subsequent-system impacts (SC:H/SI:H) reflect that SMM compromise can breach hypervisor isolation on multi-tenant Xeon hosts, affecting co-located workloads. The CPE string provided by the reporter is malformed - it reproduces the vulnerability description text rather than structured product identifiers - so exact processor model and stepping information must be obtained directly from Intel advisory INTEL-SA-01439.
RemediationAI
The primary remediation is to apply the firmware update identified in Intel Security Advisory INTEL-SA-01439 at https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01439.html. Because Intel distributes Xeon platform firmware through OEM server vendors rather than directly, operators should obtain updated firmware packages from their hardware vendor - Dell, HPE, Lenovo, Supermicro, or equivalent - and apply updates according to their standard firmware maintenance procedures. No exact patched firmware version is independently confirmed from the data available to this analysis; verify the specific fixed firmware revision in the Intel advisory before deploying. While awaiting patching, the most effective compensating control is strict privileged account hygiene: audit, reduce, and monitor who holds administrator or root-level OS access on affected Xeon systems, since PR:H is a hard exploitation prerequisite. Enabling and enforcing UEFI Secure Boot, Intel Boot Guard, and hardware SMM protections where available further constrains the attack surface, though these controls carry a configuration overhead trade-off. Restricting or disabling remote management interfaces (BMC/IPMI) that could serve as a path to elevated local access provides additional hardening, at the cost of reduced out-of-band manageability.
LibreNMS before 24.10.0 allows a remote attacker to execute arbitrary code via OS command injection involving AboutContr
Reachable assertion in Open5GS up to version 2.7.6 allows remote unauthenticated attackers to crash the Diameter CER han
A Command Injection issue in the payload build page in BYOB (Build Your Own Botnet) 2.0 allows attackers to execute arbi
Denial of service in Open5GS 2.7.6 and earlier allows network-adjacent attackers with low-privilege Diameter Gx peer acc
Denial of service in Open5GS HSS (Home Subscriber Server) versions 2.7.0 through 2.7.6 is triggered remotely by manipula
Remote command injection in Control Web Panel allows unauthenticated attackers to execute arbitrary OS commands as root
LINQPad before 5.52.01 Pro edition is vulnerable to Unsafe Deserialization in LINQPad.AutoRefManager::PopulateFromCache(
Remote code execution in dash-uploader (Python package for Plotly Dash) versions 0.1.0 through 0.7.0a2 allows unauthenti
Command injection in LiteLLM 1.18.10 lets attackers who can configure MCP (Model Context Protocol) servers supply arbitr
SQL injection in AzuraCast's backup restore flow (versions up to and including 0.23.7) lets an attacker achieve privileg
Arbitrary file read in Yu AI Code Mother v4.3 lets anonymous, remote attackers retrieve files outside the intended previ
Remote code execution in APScheduler (all versions through 3.10.x and 4.0.0a5) is achievable when applications deseriali
Same weakness CWE-284 – Improper Access Control
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-56509
GHSA-x334-5fcx-5jhr