EUVD-2026-56471
GHSA-4hx7-cvpj-f259
Severity by source
CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/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
Local-only access, Ring-0 privileges required, high complexity with specific prerequisites; scope changes because TD confidentiality boundary is crossed, affecting subsequent system.
Primary rating from Vendor (intel).
CVSS VectorVendor: intel
Lifecycle Timeline
1DescriptionCVE.org
Insecure storage of sensitive information in the Intel(R) TDX module for some Intel(R) platform within Ring 0: Trust Domain may allow information disclosure. System software 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 (high), integrity (none) and availability (none) impacts.
AnalysisAI
Insecure sensitive data storage in the Intel Trust Domain Extensions (TDX) module exposes confidential memory to privileged local adversaries on affected Intel platforms. The flaw, classified under CWE-922, allows a Ring-0 system software attacker - such as a compromised or malicious hypervisor or host OS kernel - to read data that should be protected within a Trust Domain, breaking TDX's core confidential computing isolation guarantee. No public exploit has been identified at time of analysis, and exploitation demands high privilege, high complexity, and specific attack prerequisites, materially constraining real-world risk despite the high confidentiality impact rating.
Technical ContextAI
Intel TDX (Trust Domain Extensions) is a hardware-enforced confidential computing technology available on select Intel Xeon Scalable (Sapphire Rapids, 4th Gen and later) and compatible client platforms. TDX creates hardware-isolated Trust Domains (TDs) - essentially confidential virtual machines - that are protected from the host hypervisor, host OS, and other VMs via CPU-enforced memory encryption and access controls rooted in the Intel TDX module firmware running at Ring 0. CWE-922 (Insecure Storage of Sensitive Information) indicates that sensitive data - likely cryptographic material, TD secrets, or attestation data - is being stored in memory or registers in a manner accessible to a sufficiently privileged attacker on the same physical host. The CPE string (cpe:2.3:a:n/a:intel(r)_platform:*:*:*:*:*:*:*:*) is broad and under-specified; affected platform scope is deferred to Intel's advisory INTEL-SA-01436. The CVSS 4.0 vector AV:L/AC:H/AT:P/PR:H indicates the vulnerability is local, high complexity, requires specific attack conditions (AT:P), and demands Ring-0 / hypervisor-equivalent privileges.
RemediationAI
The primary remediation is to apply Intel's firmware or microcode update addressing INTEL-SA-01436, available through the Intel Product Security Incident Response advisory at https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01436.html. The exact patched TDX module version is not independently confirmed from the available data - consult the advisory directly for the specific firmware revision to target. Platform vendors (OEMs, cloud providers) typically distribute TDX module updates via BIOS/UEFI firmware updates; check your platform vendor's support channel for a validated update package. As a compensating control while patching is pending, organizations can restrict physical or logical access to the host Ring-0 environment and audit hypervisor integrity continuously. Disabling TDX entirely via BIOS settings eliminates the attack surface at the cost of losing confidential computing capabilities for tenant workloads - a significant operational trade-off in multi-tenant deployments. No patch version was independently confirmed from the data available; treat the advisory as the definitive source.
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-922 – Insecure Storage of Sensitive Information
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today