CVE-2008-1103 json
Multiple unspecified vulnerabilities in Blender have unknown impact and attack vectors, related to "temporary file issues."
published 2008-04-28 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-1112
- cvss
- 6.9
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
Multiple unspecified vulnerabilities in Blender have unknown impact and attack vectors, related to "temporary file issues."
Patch / fix
- blender Debian 14, Debian 13, Debian 12 2.40-1
debian advisories DEBIAN-CVE-2008-1103
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2008-1103 updated
Blender insecure temporary file usage
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.9 | AV:L/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-59 Improper Link Resolution Before File Access
References
-
lists.opensuse.org
/opensuse-security-announce/2008-04/msg00011.html
vendor-advisory
-
mandriva.com
/security/advisories?name=MDVSA-2008:204
vendor-advisory
-
gentoo.org
/security/en/glsa/glsa-200805-12.xml
vendor-advisory
-
secunia.com
/advisories/29842
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/30151
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/29957
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/28936
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/42153
vdb-entry
Sources
- CVE List CVE-2008-1103
- NVD CVE-2008-1103
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.