CVE-2012-6076 json
Inkscape before 0.48.4 reads .eps files from /tmp instead of the current directory, which might cause Inkspace to process unintended files,…
published 2013-03-12 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5950
- cvss
- 4.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
Inkscape before 0.48.4 reads .eps files from /tmp instead of the current directory, which might cause Inkspace to process unintended files, allow local users to obtain sensitive information, and possibly have other unspecified impacts.
Patch / fix
- inkscape Debian 14, Debian 13, Debian 12 0.48.3.1-1.3
debian advisories DEBIAN-CVE-2012-6076
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-2012-6076 updated cvss 1.9
inkscape: Reads .eps files from /tmp instead of current working directory
-
Red Hat Enterprise Linux 6 inkscape, inkscape-viewaffected: no fix planned “Will not fix”
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.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.4 | AV:L/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
-
ubuntu.com
/usn/USN-1712-1
vendor-advisory
-
lists.opensuse.org
/opensuse-updates/2013-02/msg00041.html
vendor-advisory
-
lists.opensuse.org
/opensuse-updates/2013-02/msg00043.html
vendor-advisory
-
openwall.com
/lists/oss-security/2012/12/30/2
mailing-list
- bugs.launchpad.net /inkscape/+bug/911146
- bugs.debian.org /cgi-bin/bugreport.cgi?bug=654341
Sources
- CVE List CVE-2012-6076
- NVD CVE-2012-6076
Fencer Intel 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.