dbcve.org
Heap-based Buffer OverflowWeakness · CWE-122

CVE-2025-54951

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-07
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
A group of related buffer overflow vulnerabilities in the loading of ExecuTorch models can cause the runtime to crash and potentially result in code execution or other undesirable effects. This issue affects ExecuTorch prior to commit cea9b23aa8ff78aff92829a466da97461cc7930c.

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 · moderate confidence

Buffer overflow vulnerabilities in ExecuTorch's model loading functionality allow attackers to potentially execute arbitrary code or crash the runtime by loading specially crafted malicious models. The vulnerabilities exist in the model parsing/deserialization path prior to commit cea9b23aa8ff78aff92829a466da97461cc7930c.

MitigationUpgrade ExecuTorch to commit cea9b23aa8ff78aff92829a466da97461cc7930c or later. Until then, only load models from trusted sources and implement input validation on model files before loading.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate ExecuTorch installation
    Identify where ExecuTorch is installed in your environment by searching for the ExecuTorch directory or checking your Python packages (e.g., pip show executorch or find / -name '*executorch*' -type d 2>/dev/null)
    Affected if ExecuTorch is present in your environment
  2. Determine ExecuTorch version or commit
    Check the installed version by running 'pip show executorch' or inspecting the git commit hash if using a source installation (look for .git directory or check version metadata)
    Affected if The version or commit cannot be determined or is from before the fix
  3. Compare to the fixed commit
    Compare your installed commit hash to cea9b23aa8ff78aff92829a466da97461cc7930c - if your commit is older or the version predates this fix, you are running a vulnerable version
    Affected if Your ExecuTorch version is before commit cea9b23aa8ff78aff92829a466da97461cc7930c
  4. Assess model loading exposure
    Review your application code to determine if it loads ExecuTorch models from external or untrusted sources (e.g., user-uploaded files, network endpoints, third-party model repositories)
    Affected if Your application loads models from untrusted or external sources without validation

You are affected if ExecuTorch is installed and the version/commit is older than cea9b23aa8ff78aff92829a466da97461cc7930c, especially if your application loads models from untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade ExecuTorch to commit cea9b23aa8ff78aff92829a466da97461cc7930c or later. Until then, only load models from trusted sources and implement input validation on model files before loading.

Recommended fix High confidence

Any ExecuTorch version/commit at or after cea9b23aa8ff78aff92829a466da97461cc7930c

  1. Identify the current ExecuTorch version in use by checking the installed package version or git commit hash
  2. Upgrade to a version of ExecuTorch that includes the fix from commit cea9b23aa8ff78aff92829a466da97461cc7930c
  3. Verify the upgrade by checking that the git commit hash of the installed ExecuTorch is later than or equal to cea9b23aa8ff78aff92829a466da97461cc7930c
  4. Test the model loading functionality to ensure the vulnerability is resolved and the runtime functions correctly
Caveat Review ExecuTorch release notes for any breaking changes between the current version and the target upgrade version, particularly if upgrading across major releases

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54951 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54951 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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