Skip to content
Fencer Intel
critical 9.1

CVE-2018-12713 json

GIMP through 2.10.2 makes g_get_tmp_dir calls to establish temporary filenames, which may result in a filename that already exists, as demo…

published 8y ago modified 4mo ago also EUVD-2018-4666

cvss
9.1
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

GIMP through 2.10.2 makes g_get_tmp_dir calls to establish temporary filenames, which may result in a filename that already exists, as demonstrated by the gimp_write_and_read_file function in app/tests/test-xcf.c. This might be leveraged by attackers to overwrite files or read file content that was intended to be private.

Patch / fix

  • gimp Debian 14, Debian 13 3.0.0~RC1-4

debian advisories DEBIAN-CVE-2018-12713

Is CVE-2018-12713 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2018-12713 updated cvss 6.7

gimp: predictable temporary file name in test-xcf.c unit test

  • Red Hat Enterprise Linux 7 gimp, gimp-libs, gimp-devel-tools Red Hat Enterprise Linux 8 gimp, pygtk2, gimp-libs, pygobject2, python2-cairo, pygtk2-codegen, +3 more
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 5 gimp Red Hat Enterprise Linux 6 gimp, gimp-libs, gimp-devel-tools, gimp-help-browser
    not 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

1.92% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD 2.0 6.4 AV:N/AC:L/Au:N/C:P/I:P/A:N

References

Sources

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.