Synced 07 Nov 2026 15:45 UTC Account
← Blender

Blender vulnerabilities: known CVEs & security history

Blender · Media / 3D · 5 tracked CVEs · 0 actively exploited · updated November 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Blender release lines — 5 in total. A CVE here doesn't mean your version is affected — check Blender's current status and the safe version to run.

5
known CVEs
0
actively exploited (KEV)
0
critical severity
0
ransomware-linked

Known Blender CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2026-119722 high 7.8 0% 2026
CVE-2026-119719 high 7.8 0% 2026
CVE-2026-119718 high 7.8 0% 2026
CVE-2026-119721 medium 6.1 0% 2026
CVE-2026-119720 medium 5.5 0% 2026

Is my Blender version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Blender version → · Monitor Blender for new CVEs →

Blender vulnerabilities — frequently asked

How many known vulnerabilities does Blender have?

IsItPatched tracks 5 CVEs for Blender. 0 are critical-severity and 3 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Blender have any actively-exploited vulnerabilities?

None of Blender's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Blender vulnerability?

Among tracked issues, CVE-2026-119722 (HIGH, CVSS 7.8) ranks highest — a Out-of-bounds read weakness.

Is Blender safe to use?

It depends on the version. The latest supported Blender release (5.2.3) clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Blender security status · Blender end-of-life · actively-exploited CVEs. Always verify against Blender's advisories — see our disclaimer.