Libexif is a small, narrowly scoped EXIF image-metadata parsing library that sits deep in the software supply chain of image viewers, cameras, and media applications despite its modest product footprint. The vendor's prominence in the landscape stems from ubiquitous downstream integration rather than direct deployment; a single flaw in libexif can propagate across every application that links the library. Vulnerabilities affecting libexif cluster around memory-safety and resource-handling issues, including improper buffer restrictions, integer overflow and underflow conditions, out-of-bounds reads, and unbounded resource allocation—weaknesses endemic to a C-based parser handling untrusted image data. These flaws are characteristic of parsing libraries exposed to attacker-controlled input, making inventory of downstream products that bundle libexif more operationally relevant than tracking the library alone. Current exploitation activity, severity distribution, and exposure metrics are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Libexif Project over time
Signals from CVEs in this vendor scope (27 CVEs).
27 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2007-2645HIGH Integer overflow in the exif_data_load_data_entry function in exif-data.c in libexif before 0.6.14 allows user-assisted remote attackers to cause a denial of service (crash) or pos | May 14, 2007 | 9.3 | 39 | NO | YES |
CVE-2017-7544CRITICAL libexif through 0.6.21 is vulnerable to out-of-bounds heap read vulnerability in exif_data_save_data_entry function in libexif/exif-data.c caused by improper length computation of | Sep 21, 2017 | 9.1 | 30 | NO | NO |
CVE-2026-40386HIGH In libexif through 0.6.25, an integer underflow in size checking for Fuji and Olympus MakerNote decoding could be used by attackers to crash or leak information out of libexif-usin | Apr 12, 2026 | 7.1 | 29 | NO | NO |
CVE-2026-40385HIGH In libexif through 0.6.25, an unsigned 32bit integer overflow in Nikon MakerNote handling could be used by local attackers to cause crashes or information leaks. This only affects | Apr 12, 2026 | 7.1 | 28 | NO | NO |
CVE-2020-13113HIGH An issue was discovered in libexif before 0.6.22. Use of uninitialized memory in EXIF Makernote handling could lead to crashes and potential use-after-free conditions. | May 21, 2020 | 8.2 | 28 | NO | NO |
CVE-2026-32775HIGH libexif through 0.6.25 has a flaw in decoding MakerNotes. If the exif_mnote_data_get_value function gets passed in a 0 size, the passed in-buffer would be overwritten due to an int | Mar 16, 2026 | 7.8 | 26 | NO | NO |
CVE-2020-0181HIGH In exif_data_load_data_thumbnail of exif-data.c, there is a possible denial of service due to an integer overflow. This could lead to remote denial of service with no additional ex | Jun 11, 2020 | 7.5 | 26 | NO | NO |
CVE-2020-13114HIGH An issue was discovered in libexif before 0.6.22. An unrestricted size in handling Canon EXIF MakerNote data could lead to consumption of large amounts of compute time for decoding | May 21, 2020 | 7.5 | 26 | NO | NO |
CVE-2012-2814HIGH Buffer overflow in the exif_entry_format_value function in exif-entry.c in the EXIF Tag Parsing Library (aka libexif) 0.6.20 allows remote attackers to cause a denial of service or | Jul 13, 2012 | 7.5 | 26 | NO | NO |
CVE-2020-13112CRITICAL An issue was discovered in libexif before 0.6.22. Several buffer over-reads in EXIF MakerNote handling could lead to information disclosure and crashes. This is different from CVE- | May 21, 2020 | 9.1 | 25 | NO | NO |
Signals from CVEs in this vendor scope (27 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Libexif Project.
Media articles that mention a CVE ID that affects a product developed by Libexif Project — matched by CVE ID, not by vendor name.