CVE-2024-36348VulnerabilityPublished 8 Jul 2025Updated 4 Nov 2025

CVE-2024-36348: AMD EPYC™ 7002 Series Processors · Exposure of Sensitive Information during Transient Execution

Affects AMD EPYC™ 7002 Series ProcessorsSource CVE Database V5

Not known to be exploited · CVSS 3.8 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

3.8Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
AMD AMD EPYC™ 7002 Series Processors	Affected *	Fixed in–

AI-suggested

1. Monitor AMD and relevant OS vendors for microcode and firmware updates addressing this vulnerability and apply them promptly once available. 2. Restrict local code execution privileges to trusted users and processes to reduce the risk of local exploitation. 3. Employ strict containerization and virtualization isolation to limit speculative execution exposure between tenants. 4. Use security features such as Kernel Page-Table Isolation (KPTI) and other OS-level mitigations that reduce speculative execution side-channel risks. 5. Conduct regular audits of local user activities and privilege escalations to detect potential exploitation attempts. 6. Harden system configurations to minimize unnecessary local access and disable unneeded services that could be exploited to run code locally. 7. Engage with hardware and software vendors for guidance on best practices specific to AMD EPYC 7002 processors in your environment.

Description

A transient execution vulnerability in some AMD processors may allow a user process to infer the control registers speculatively even if UMIP feature is enabled, potentially resulting in information leakage.

Impact

For European organizations, especially those operating cloud services, data centers, or high-performance computing environments using AMD EPYC 7002 processors, this vulnerability could lead to leakage of sensitive control register information. While the direct impact is low, the leaked data could be leveraged in chained attacks to bypass security controls or escalate privileges. Confidentiality breaches could affect sensitive workloads, intellectual property, or cryptographic operations relying on processor state secrecy. The risk is heightened in shared infrastructure environments common in Europe’s cloud and enterprise sectors. However, since exploitation requires local access and no known exploits exist, the immediate threat is limited. Organizations handling critical infrastructure or sensitive data should consider this vulnerability in their risk assessments and incident response plans.

CWE-1420Exposure of Sensitive Information during Transient Execution (opens in a new tab)
Base weakness
A processor event or prediction may allow incorrect operations (or correct operations with incorrect data) to execute transiently, potentially exposing data over a covert channel.
Architecture and Design
The hardware designer can attempt to prevent transient execution from causing observable discrepancies in specific covert channels.
Requirements
Processor designers may expose instructions or other architectural features that allow software to mitigate the effects of transient execution, but without disabling predictors. These features may also help to limit opportunities for data exposure.
Requirements
Processor designers may expose registers (for example, control registers or model-specific registers) that allow privileged and/or user software to disable specific predictors or other hardware features that can cause confidential data to be exposed during transient execution.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 21:39 UTC

WeaknessesCWE-1420

Technical details

References

Community reviews

Related threats