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

CVE-2026-60103

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
64/100
Remediation priority · Elevated
No privileges 5 weeks old

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
Blender 3.0.0 through 5.1.2 contains an out-of-bounds read vulnerability that allows attackers to trigger a crash or read adjacent heap memory by supplying a crafted .blend file with a malicious signed short member_index value in the SDNA block. The member_index field is used as an array index into the sdna->members[] array in sdna_expand_names() without bounds validation, allowing any value outside the allocated range to produce an invalid pointer subsequently passed to strlen(), resulting in a SIGSEGV crash or unintended heap memory disclosure.

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 confidence

Blender versions 3.0.0 through 5.1.2 have an out-of-bounds read vulnerability in the SDNA block parsing code. When parsing a crafted .blend file, the member_index field (a signed short) is used directly as an array index into the sdna->members[] array in sdna_expand_names() without bounds validation. This allows values outside the allocated range to produce an invalid pointer passed to strlen(), resulting in SIGSEGV crash or heap memory disclosure.

MitigationUpdate Blender to the latest version which includes bounds validation on the member_index field before array access. Until an official patch is available, avoid opening untrusted .blend files from unknown or untrusted sources.

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/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. Check installed Blender version
    Run 'blender --version' from command line or open Blender and go to Help > About Blender to see the version number
    Affected if The version shown is 3.0.0 through 5.1.2 (including minor versions like 3.1.0, 4.2.1, etc.)
  2. Confirm SDNA parsing is reachable
    The vulnerability triggers automatically when opening .blend files - no special feature flag needed. Verify you use Blender to open .blend files from any source.
    Affected if Blender is used to open .blend files and the version falls within 3.0.0 to 5.1.2
  3. Check for patch availability (optional)
    Look for Blender release notes or security advisories after version 5.1.2 that mention bounds validation fixes for member_index or SDNA parsing
    Affected if No subsequent version is installed that includes the bounds checking fix

You are affected if your Blender installation version is 3.0.0 through 5.1.2 and you open .blend files, as the vulnerable SDNA parsing code runs automatically when loading such files.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Blender to the latest version which includes bounds validation on the member_index field before array access. Until an official patch is available, avoid opening untrusted .blend files from unknown or untrusted sources.

Recommended fix Moderate confidence

Blender version after 5.1.2 (verify fix is included in release notes)

  1. 1. Verify the exact Blender version currently installed using Help > System Information or running `blender --version`
  2. 2. Download the latest stable Blender release from the official blender.org website
  3. 3. Uninstall the current Blender version before installing the updated version
  4. 4. Install the new Blender version and verify the installation by opening the application
  5. 5. Test that .blend files can be opened normally before resuming production work
Caveat Ensure any custom scripts or addons are compatible with the new Blender version before production use

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

Have this fixed Scoped from the published advisory
  • Consultation5.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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