Skip to content
VulniPulse
Medium6.1Red Hat Linux

Medium [CVE-2026-60103] Denial of Service and information disclosure via crafted.blend file

This medium-severity Red Hat Linux advisory covers CVE-2026-60103.

CVE-2026-60103 Published Jul 13, 2026Updated by vendor Jul 13, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

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. A flaw was found in Blender.

A remote attacker could exploit an out-of-bounds read vulnerability by providing a specially crafted.blend file. This vulnerability occurs when the application processes a malicious member_index value without proper validation, leading to an attempt to access memory outside of its allocated boundaries.

Successful exploitation can result in a denial of service, causing the application to crash, or potentially lead to the disclosure of sensitive information from the system's memory. Red Hat severity: Moderate — CVSS 6.1 (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H).

Weakness: CWE-125.

Affected versions
  • 3.0.0
  • 5.1.2

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · high-confidence parse· fetched 2 months ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.