dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2025-54950

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
An out-of-bounds access vulnerability 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 b6b7a16df5e7852d976d8c34c8a7e9a1b6f7d005.

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

An out-of-bounds access vulnerability exists in ExecuTorch's model loading mechanism. When loading malformed or crafted ExecuTorch models, the runtime accesses memory outside allocated buffers, leading to crashes and potential arbitrary code execution. This affects ExecuTorch versions prior to commit b6b7a16df5e7852d976d8c34c8a7e9a1b6f7d005.

MitigationUpdate ExecuTorch to the version containing the fix (commit b6b7a16df5e7852d976d8c34c8a7e9a1b6f7d005 or later). Re-export any models created with vulnerable versions using the patched ExecuTorch export tools, and validate model loading in affected environments.

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. Identify ExecuTorch installation
    Search for ExecuTorch files or libraries in the environment: look for 'executorch' in installed Python packages (pip list), search for libexecutorch.so or similar binaries, or check for ExecuTorch in project dependencies
    Affected if ExecuTorch is present in the environment
  2. Determine ExecuTorch version
    Run 'pip show executorch' or check the git commit hash if using a source installation: 'git -C /path/to/executorch log -1 --format=%H'
    Affected if The installed version is earlier than commit b6b7a16df5e7852d976d8c34c8a7e9a1b6f7d005 or the version cannot be determined
  3. Verify model loading feature usage
    Inspect application code that uses ExecuTorch for model loading calls: look for 'load', 'load_from_buffer', or 'deserialize' functions from the ExecuTorch runtime API
    Affected if The application loads ExecuTorch models at runtime
  4. Check model provenance controls
    Review whether the application validates or restricts the source of loaded models: check for model signature verification, allowlist of trusted model sources, or network isolation of model loading
    Affected if Untrusted or externally-sourced models can be loaded without validation

A user is affected if ExecuTorch is installed with a version prior to commit b6b7a16df5e7852d976d8c34c8a7e9a1b6f7d005 and the application loads ExecuTorch models, especially 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

Update ExecuTorch to the version containing the fix (commit b6b7a16df5e7852d976d8c34c8a7e9a1b6f7d005 or later). Re-export any models created with vulnerable versions using the patched ExecuTorch export tools, and validate model loading in affected environments.

Recommended fix Moderate confidence

Update to the latest ExecuTorch release or ensure you are on/after commit b6b7a16df5e7852d976d8c34c8a7e9a1b6f7d005

  1. Identify your current ExecuTorch version or commit hash by checking your dependency lock file or running `git log` in your ExecuTorch repository
  2. If you have a local installation, navigate to your ExecuTorch directory and run `git fetch origin` to get the latest commits
  3. Run `git log --oneline -1` to confirm your current commit is before b6b7a16df5e7852d976d8c34c8a7e9a1b6f7d005
  4. Apply the fix by running `git cherry-pick b6b7a16df5e7852d976d8c34c8a7e9a1b6f7d005` or `git pull` if you want the latest version
  5. Rebuild ExecuTorch after applying the fix: follow your existing build process (typically `cmake` and `cmake --build`)
  6. Test that model loading functionality still works correctly after the update
  7. Verify the fix is applied by confirming the commit hash in your installed version
Caveat Minimal risk - this is a security fix for an out-of-bounds read; however, rebuilds may introduce compatibility issues with custom operators or model formats if not thoroughly tested

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54950 — 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-54950 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