CVE-2025-54949VulnerabilityPublished 7 Aug 2025Updated 12 Aug 2025

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

Affects Meta Platforms ExecuTorchSource CVE Database V5

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

9.8Critical

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
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: 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: 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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 7 Aug 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
Meta Platforms, Inc ExecuTorch	Affected =0	Fixed in–

AI-suggested

1. Immediate mitigation should include isolating ExecuTorch workloads in segmented network environments to limit exposure. 2. Employ runtime application self-protection (RASP) and memory protection mechanisms such as Address Space Layout Randomization (ASLR) and Data Execution Prevention (DEP) to reduce exploitation success. 3. Monitor network traffic and logs for unusual activity related to ExecuTorch model loading, including anomalous input sizes or malformed model files. 4. Restrict access to ExecuTorch services to trusted users and systems only, using network-level controls and strong authentication. 5. Implement strict input validation and sandboxing for model files before loading them into ExecuTorch environments. 6. Stay alert for official patches or updates from Meta Platforms and apply them promptly once available. 7. Conduct regular security assessments and penetration testing focused on AI infrastructure to detect similar vulnerabilities. 8. Develop incident response plans specifically addressing AI platform compromises to minimize damage in case of exploitation.

Description

A heap buffer overflow vulnerability in the loading of ExecuTorch models can potentially result in code execution or other undesirable effects. This issue affects ExecuTorch prior to commit ede82493dae6d2d43f8c424e7be4721abe5242be

Impact

For European organizations, the impact of CVE-2025-54949 can be severe. Many enterprises and research institutions in Europe utilize AI frameworks and tools from Meta Platforms for machine learning workloads, data analysis, and AI-driven services. Exploitation of this vulnerability could lead to unauthorized code execution, data breaches, disruption of AI services, and potential lateral movement within corporate networks. This could compromise sensitive data, intellectual property, and critical AI model integrity. Additionally, organizations relying on AI for decision-making or operational automation may face significant operational disruptions. Given the criticality and remote exploitability, attackers could leverage this vulnerability to deploy ransomware, steal confidential information, or sabotage AI-driven processes. The lack of patches at the time of disclosure increases the urgency for European organizations to implement mitigations to protect their AI infrastructure and maintain compliance with data protection regulations such as GDPR.

Summary

CVE-2025-54949 is a critical heap-based buffer overflow vulnerability (CWE-122) found in Meta Platforms, Inc's ExecuTorch product. ExecuTorch is a framework or tool related to loading and executing machine learning models. The vulnerability arises during the loading process of ExecuTorch models, where improper handling of heap memory leads to a buffer overflow condition. This flaw can be exploited remotely without any authentication or user interaction, as indicated by the CVSS vector (AV:N/AC:L/PR:N/UI:N). Successful exploitation allows an attacker to execute arbitrary code with the privileges of the ExecuTorch process, potentially leading to full system compromise. The CVSS v3.1 base score is 9.8, reflecting its critical severity due to high impact on confidentiality, integrity, and availability, combined with ease of exploitation. Although no known exploits are reported in the wild yet, the nature of the vulnerability and the widespread use of Meta's AI tools suggest a high risk of future exploitation. The vulnerability is particularly dangerous because it can be triggered remotely without any prerequisites, making it a prime target for attackers aiming to compromise AI infrastructure or systems running ExecuTorch models.

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 15 Aug 2025, 01:04 UTC

WeaknessesCWE-122

Technical details

References

Community reviews

Related threats