CVE-2025-54949
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHeap buffer overflow vulnerability in ExecuTorch model loading that could allow an attacker to achieve code execution through specially crafted malicious models. The vulnerability exists in how ExecuTorch handles model deserialization/parsing prior to the fix commit.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if ExecuTorch is present in your environmentSearch for ExecuTorch installation: check for 'executorch' directory, library files (libexecutorch.*), or Python package (pip list | grep executorch). Also check if your application links against ExecuTorch libraries.Affected if ExecuTorch is not found in your environment, you are not affected by this vulnerability.
-
Determine the ExecuTorch version or commit hashIf ExecuTorch is installed, run 'git log --oneline -1' inside the ExecuTorch repository, or check the library version if exposed via 'executorch --version'. Alternatively, look at the commit history for commit ede82493dae6d2d43f8c424e7be4721abe5242be.Affected if The installed commit precedes ede82493dae6d2d43f8c424e7be4721abe5242be, indicating the deserialization fix is not applied.
-
Verify if model loading functionality is usedInspect your application code to determine if ExecuTorch's model loading APIs (such as ::torch::executor::load method or similar deserialization functions) are called at runtime. Check for any .pte or ExecuTorch model file loading in your codebase.Affected if Your application does not load ExecuTorch models, the buffer overflow cannot be triggered.
-
Assess model trust boundaryReview whether your application loads models from untrusted sources (user-uploaded files, network-fetched models, third-party repositories). Check configuration files and runtime permissions for model loading paths.Affected if Only trusted, locally-controlled models are loaded, the exploit path is not reachable regardless of version.
You are affected if ExecuTorch is present, the installed version predates commit ede82493, and your application loads ExecuTorch models from untrusted or external sources.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate ExecuTorch to commit ede82493dae6d2d43f8c424e7be4721abe5242be or later. Until patched, avoid loading untrusted ExecuTorch models.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54949 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54949 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data