CVE-2025-30402VulnerabilityPublished 11 Jul 2025

CVE-2025-30402: Meta Platforms ExecuTorch · Heap-based Buffer Overflow

Affects Meta Platforms ExecuTorchSource CVE Database V5

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

8.1High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: High

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 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 26 Oct 2026.

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
Meta Platforms, Inc ExecuTorch	Affected =0	Fixed in–

AI-suggested

1. Immediate application of patches or updates from Meta Platforms once officially released is critical. Organizations should track the specific commit (93b1a0c15f7eda49b2bc46b5b4c49557b4e9810f) and apply the fix to all ExecuTorch deployments. 2. Until patches are available, restrict access to ExecuTorch runtimes to trusted users and networks only, minimizing exposure to untrusted inputs that could trigger the vulnerability. 3. Implement strict input validation and sanitization on all data or method payloads submitted to ExecuTorch to reduce the risk of maliciously crafted inputs causing buffer overflows. 4. Employ runtime protections such as heap memory protection mechanisms (e.g., heap canaries, ASLR, DEP) to mitigate exploitation impact. 5. Monitor ExecuTorch runtime logs and system behavior for crashes or anomalies indicative of attempted exploitation. 6. Conduct thorough code reviews and security testing on any custom extensions or integrations with ExecuTorch to identify and remediate similar memory safety issues. 7. Incorporate ExecuTorch vulnerability awareness into incident response plans, preparing for potential exploitation scenarios. 8. Engage with Meta’s security advisories and community forums to stay informed about updates, patches, and exploit developments.

Description

A heap-buffer-overflow vulnerability in the loading of ExecuTorch methods can cause the runtime to crash and potentially result in code execution or other undesirable effects. This issue affects ExecuTorch prior to commit 93b1a0c15f7eda49b2bc46b5b4c49557b4e9810f

Impact

For European organizations, the impact of CVE-2025-30402 depends largely on the adoption of ExecuTorch within their infrastructure. Organizations leveraging Meta’s AI or machine learning runtimes, particularly those integrating ExecuTorch for model execution or development, could face significant risks. Exploitation could lead to runtime crashes causing service disruptions or denial of service, impacting availability of critical AI-driven applications. More severely, successful exploitation could allow attackers to execute arbitrary code within the context of the vulnerable process, potentially leading to full system compromise, data exfiltration, or lateral movement within networks. This is particularly concerning for sectors relying on AI for sensitive operations such as finance, healthcare, telecommunications, and critical infrastructure. The absence of known exploits currently reduces immediate risk, but the vulnerability’s presence in a widely used AI runtime component could attract attackers once exploit techniques mature. European organizations must consider the confidentiality, integrity, and availability risks posed by this vulnerability, especially in environments where ExecuTorch processes untrusted or external inputs. The potential for code execution elevates the threat to a high level, warranting urgent attention to patching and mitigation.

CWE-122Heap-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #16
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Pre-design: Use a language or compiler that performs automatic bounds checking.
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
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 11 Jul 2025, 18:01 UTC

WeaknessesCWE-122

Technical details

References

Community reviews

Related threats