dbcve.org
Integer OverflowWeakness · CWE-190

CVE-2025-30405

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 integer overflow vulnerability in the loading of ExecuTorch models can cause objects to be placed outside their allocated memory area, potentially resulting in code execution or other undesirable effects. This issue affects ExecuTorch prior to commit 0830af8207240df8d7f35b984cdf8bc35d74fa73.

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 integer overflow vulnerability exists in ExecuTorch's model loading functionality. When parsing ExecuTorch models, certain size calculations or memory allocations do not properly validate integer values, allowing an attacker to cause memory corruption by placing objects outside their allocated buffer boundaries, potentially leading to arbitrary code execution.

MitigationUpgrade ExecuTorch to version after commit 0830af8207240df8d7f35b984cdf8bc35d74fa73 which contains the fix for this integer overflow. If upgrading is not immediately possible, restrict model loading to 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. Confirm ExecuTorch installation
    Search for ExecuTorch in your environment: check Python packages (pip list | grep -i executorch), look for the executorch directory in site-packages, or check if any application code imports executorch
    Affected if ExecuTorch is present in the environment
  2. Identify ExecuTorch version or commit
    Run 'pip show executorch' to get the version number, or check git history if built from source. Look for the version string or git commit hash in the installed package metadata
    Affected if The version/commit cannot be determined or is earlier than 0830af8207240df8d7f35b984cdf8bc35d74fa73
  3. Compare against fixed version
    Compare your installed version string or commit hash to the fixed commit 0830af8207240df8d7f35b984cdf8bc35d74fa73. If using a version number, any release built before this commit fix is considered vulnerable
    Affected if Your installed version predates the fix commit 0830af8207240df8d7f35b984cdf8bc35d74fa73
  4. Assess model loading context
    Identify how ExecuTorch models are loaded in your environment. Check application code for ExecuTorch model loading paths, such as 'torch.export.load()' or custom model loading routines that parse ExecuTorch files
    Affected if Models are loaded from untrusted or external sources without prior validation

You are affected if ExecuTorch is installed and your version predates commit 0830af8207240df8d7f35b984cdf8bc35d74fa73, especially if you load models from external or 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 version after commit 0830af8207240df8d7f35b984cdf8bc35d74fa73 which contains the fix for this integer overflow. If upgrading is not immediately possible, restrict model loading to trusted sources and implement input validation on model files before loading.

Recommended fix Moderate confidence

Any ExecuTorch release or commit after 0830af8207240df8d7f35b984cdf8bc35d74fa73

  1. Identify the current ExecuTorch version in use by checking the installed package version or git commit
  2. Navigate to the ExecuTorch repository at https://github.com/pytorch/executorch
  3. Locate and review the fix commit: https://github.com/pytorch/executorch/commit/0830af8207240df8d7f35b984cdf8bc35d74fa73
  4. Upgrade to a release version that includes this commit, or cherry-pick/apply the fix from commit 0830af8207240df8d7f35b984cdf8bc35d74fa73 if building from source
  5. Verify the upgrade by confirming the installed ExecuTorch commit is later than 0830af8207240df8d7f35b984cdf8bc35d74fa73
  6. Test ExecuTorch model loading functionality to confirm the integer overflow vulnerability is resolved

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 / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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