CVE-2024-7881VulnerabilityPublished 28 Jan 2025Updated 18 Nov 2025

CVE-2024-7881: Arm Neoverse V2 · Exposure of Sensitive Information caused by Incorrect Data Forwarding during Transient Execution

Affects Arm Neoverse V2Source CVE Database V5

Not known to be exploited · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.1Medium

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

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 28 Jan 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-25.

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
Arm Neoverse V2	Affected =0	Fixed in–

AI-suggested

Mitigation of CVE-2024-7881 requires a multi-layered approach. First and foremost, organizations should monitor vendor communications closely and apply microcode or firmware updates as soon as they become available from Arm or device manufacturers. Until patches are released, restrict local access to systems running Arm Neoverse V2 processors by enforcing strict access controls, including multi-factor authentication and least privilege principles. Employ robust monitoring and anomaly detection to identify unusual local activities that could indicate exploitation attempts. Consider isolating critical workloads or sensitive data on hardware not affected by this vulnerability or within virtualized environments with strong isolation guarantees. Additionally, implement software-level mitigations such as disabling or limiting speculative execution features if supported and feasible, understanding the potential performance trade-offs. Regularly audit and update security policies to address insider threat risks. Finally, ensure incident response plans include procedures for handling potential data leakage scenarios related to this vulnerability.

Description

An unprivileged context can trigger a data memory-dependent prefetch engine to fetch the contents of a privileged location and consume those contents as an address that is also dereferenced.

Impact

For European organizations, the primary impact of CVE-2024-7881 is the potential unauthorized disclosure of sensitive information residing in privileged memory areas. This could include cryptographic keys, system credentials, or other confidential data critical to secure operations. Organizations relying on Arm Neoverse V2-based infrastructure—commonly found in cloud data centers, telecom equipment, and edge computing devices—may face increased risk of insider threats or local attackers gaining access to sensitive data. While the vulnerability does not affect system integrity or availability, the confidentiality breach could undermine trust, lead to regulatory non-compliance (e.g., GDPR), and facilitate further attacks if sensitive credentials are exposed. The requirement for local access limits remote exploitation, but insider threats or compromised local accounts remain a concern. The absence of known exploits in the wild currently reduces immediate risk, but the medium severity rating and lack of patches necessitate proactive risk management. European critical infrastructure sectors, including finance, telecommunications, and government, may be particularly sensitive to such data leaks.

CWE-1422Exposure of Sensitive Information caused by Incorrect Data Forwarding during Transient Execution (opens in a new tab)
Base weakness
A processor event or prediction may allow incorrect or stale data to be forwarded to transient operations, 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, system software vendors, or other agents may choose to restrict the ability of unprivileged software to access to high-resolution timers that are commonly used to monitor 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.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

developer.arm.com/Arm%20Security%20Center/Arm%20CPU%20Vulnerability%20CVE-2024-7881 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Nov 2025, 13:55 UTC

WeaknessesCWE-1422

Technical details

References

Community reviews

Related threats