Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain high-privilege access within TDX guest
-
DeliveryTrigger incorrect calculation in Ring 3 guest software
-
ExploitExploit resulting privilege state
-
ExecutionEscalate beyond authorized guest privilege level
-
ImpactAccess sensitive data or operations within trust domain
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Calculation correctness
|
| Exploitation Conditions | Exploitation requires local access to a system running Intel TDX Guest software prior to version 0.3.1 on Intel TDX-capable hardware (Sapphire Rapids or later), combined with a high-privilege account within the guest OS - described explicitly as a 'system software adversary with a privileged user.' No user interaction, no specialized internal knowledge (AT:N per CVSS 4.0), and no non-default configuration are required beyond that privileged foothold. The vulnerability is bounded to intra-guest privilege escalation: subsequent-system impacts are rated None across confidentiality, integrity, and availability, meaning exploitation cannot break out to the host hypervisor or affect co-resident trust domains. Limiting factors that reduce real-world exploitability: requires physical or authenticated local session with high privileges, affects only deployments using Intel TDX hardware and this specific guest software stack, and produces only low-level C/I/A impact within the guest - not a full domain compromise. |
| Impact | The CVSS 4.0 score of 4.6 (Medium) accurately reflects a tightly scoped vulnerability: the local attack vector (AV:L) and high privileges required (PR:H) confine the threat to adversaries who already hold elevated access inside a running TDX guest. Low impact ratings across Confidentiality, Integrity, and Availability (VC:L/VI:L/VA:L) and zero subsequent-system impact (SC:N/SI:N/SA:N) confirm that exploitation cannot cascade from the guest to the host or hypervisor - the primary security boundary TDX is designed to enforce remains intact. No EPSS data was included in the intelligence feed; without it, exploitation probability cannot be quantified, though the high-privilege prerequisite strongly suppresses opportunistic risk. No CISA KEV listing and no public proof-of-concept exist at time of analysis. The description's framing - 'system software adversary with a privileged user' - points to insider-threat or compromised-privileged-account scenarios within confidential computing deployments. For any organization not running TDX workloads on Sapphire Rapids or later hardware with this specific guest software, the vulnerability has zero applicability. The CVSS score and impact ratings are internally consistent with the description; no conflicting signals were identified across the available data sources. |
| Exploit ScenarioDerived | A privileged user or compromised high-privilege account within an Intel TDX guest virtual machine crafts an operation that triggers the incorrect calculation in Ring 3 TDX guest software, producing an exploitable state that allows privilege escalation within the trust domain. No public proof-of-concept exists at time of analysis, and the requirement for pre-existing high-privilege access makes opportunistic or remote exploitation infeasible. The realistic threat actor is a malicious insider or an attacker who has already achieved privileged access within a confidential computing workload and seeks to expand beyond their authorized privilege level. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 11, 2026
Privilege escalation in Intel TDX Guest software before version 0.3.1 stems from an incorrect calculation (CWE-682) within Ring 3 user application code, enabling a local, high-privilege adversary to elevate privileges within a Trust Domain. The CVSS 4.0 vector confirms local access with high privileges required and low C/I/A impact on the vulnerable system, with no subsequent-system (host/hypervisor) impact. No public exploit exists and the vulnerability is absent from CISA KEV, placing real-world risk squarely in multi-tenant confidential computing scenarios where intra-guest privilege containment is a security objective.
RemediationAI
The definitive fix is to upgrade Intel TDX Guest software to version 0.3.1 or later, as specified by Intel advisory INTEL-SA-01462 (https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01462.html). For environments unable to patch immediately, the most effective compensating control is to restrict which accounts hold elevated privileges inside TDX guest VMs - since exploitation requires a high-privilege adversary (PR:H), minimizing the set of principals with such access directly reduces exploitability; the trade-off is potential operational friction for workloads that legitimately require broad guest-level privileges. Operators should audit all TDX guest deployments to identify instances running versions below 0.3.1 and prioritize those hosting multi-tenant or sensitive workloads. No compensating control eliminates the underlying incorrect calculation; patching to 0.3.1 is the only authoritative remediation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Intel Trust Domain Extensions (TDX) is a hardware-based confidential computing technology introduced with Intel Sapphire Rapids Xeon processors. It creates hardware-isolated guest virtual machines ('Trust Domains') using hardware memory encryption and remote attestation, isolating workloads from the host VMM, hypervisor, and peer guests. The affected component is Intel TDX Guest software (CPE: cpe:2.3:a:n/a:intel(r)_tdx_guest_software), specifically code executing in Ring 3 - the CPU's least-privileged user-mode ring, hosting normal user applications inside the guest OS. CWE-682 (Incorrect Calculation) identifies the root cause as an erroneous computation - likely an arithmetic overflow, incorrect boundary derivation, or misapplied formula in the guest software stack - that produces an exploitable privilege or memory state. Because the flaw resides in software running inside a confidential enclave, it is particularly relevant to organizations relying on TDX's isolation guarantees for workload security.
Know when N A gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
Local attack vector and high privileges required match the 'system software adversary with privileged user' description; unchanged scope reflects zero subsequent-system impact; low C/I/A aligns with vendor-reported impact ratings.
Primary rating from Vendor (intel).
CVSS VectorVendor: intel
DescriptionCVE.org
Incorrect calculation for some Intel(R) TDX Guest software before version 0.3.1 within Ring 3: User Applications 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 (low), integrity (low) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
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
EUVD-2026-56490
GHSA-wgvc-hf5h-m5h7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB