# CVE-2026-60103: Blender 3.0.0 - 5.1.2 Out-of-Bounds Read via crafted .blend SDNA block

> Attackers can cause crashes or read heap memory by providing a crafted .blend file with invalid SDNA block indices in Blender.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-60103, GHSA-m48f-fh37-4jc6, UBUNTU-CVE-2026-60103

## What is CVE-2026-60103?

CVE-2026-60103 is a medium-severity memory corruption vulnerability in blender, published on 13 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-60103?


## How do I fix CVE-2026-60103?

No fix has been published for CVE-2026-60103 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-60103 being exploited?

There is no known exploitation of CVE-2026-60103 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-60103 and fix it if it is affected.

What it is: CVE-2026-60103 is a medium-severity memory corruption vulnerability in blender, published on 13 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-60103 in the wild and no public exploit code.

Affected product: blender. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-60103/ (Markdown: https://insights.sbomify.com/CVE-2026-60103/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-60103
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-60103
- OSV: https://osv.dev/vulnerability/CVE-2026-60103

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-60103/
Summaries are generated and may contain mistakes; the official description above is the record.