CVE-2026-60103

MEDIUMPre-NVD 6.16.1—
EchelonGraph scoreHIGH confidence

Score 6.1 from GitHub Security Advisory published 2026-07-13. a secondary CVSS source baseline 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.1
EG Score
6.1(high)
EPSS
1.9%
KEV
Not listed

Published

July 13, 2026

Last Modified

July 15, 2026

Advisory Details (3)

Auto-updated Jul 13, 2026
No patch confirmed yet.
generic

Blender 3.0.0 - 5.1.2 Out-of-Bounds Read via crafted .blend SDNA block | Advisories | VulnCheck

https://www.vulncheck.com/advisories/blender-out-of-bounds-read-via-crafted-blend-sdna-block
generic

Fix several potential errors when reading corrupted DNA data. · 968972a918 - blender - Blender Projects

https://projects.blender.org/blender/blender/commit/968972a918b5ed2d534295b639c54449d7de11cd
generic

#161273 - Fix several potential errors when reading corrupted DNA data. - blender - Blender Projects

https://projects.blender.org/blender/blender/pulls/161273

Vendor Advisories for CVE-2026-60103(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 21:19 UTCEG score recompute
  2. 2026-07-15 21:19 UTCGHSA enrichment
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-14 19:37 UTCEG score recompute
  7. 2026-07-14 19:37 UTCGHSA enrichment
  8. 2026-07-13 17:53 UTCEG score recompute
  9. 2026-07-13 17:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-60103?
CVE-2026-60103 is a medium vulnerability published on July 13, 2026. 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 memberindex value in the SDNA block. The memberindex field is used as an array index into…
When was CVE-2026-60103 disclosed?
CVE-2026-60103 was first published in the National Vulnerability Database on July 13, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-60103 actively exploited?
CVE-2026-60103 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-60103?
CVE-2026-60103 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-60103?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-60103, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-60103

Explore →

Is Your Infrastructure Affected by CVE-2026-60103?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs