CVE-2026-7580: Exiftool · Code Injection
Affects ExiftoolSource CVE Database V5
Public exploit available · CVSS 4.8 Medium · fixed in 13.54 : patch Exiftool as a priority.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 13.54
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 1 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Exiftool | Affected
| Fixed in– |
GitHubexiftool/exiftoolpkg:github/exiftool/exiftoolOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Exiftool to version 13.54 or later to apply the official patch (commit 5a8b6b6ead12b39e3f32f978a4efd0233facbb01) that addresses this vulnerability. Since the vulnerability requires local access, restricting local user permissions and access can reduce risk. Patch status is confirmed by the vendor's release of version 13.54.
Description
A vulnerability was detected in Exiftool up to 13.53. Impacted is the function Process_mrld of the file lib/Image/ExifTool/GM.pm of the component JPEG/QuickTime/MOV/MP4. The manipulation of the argument -ee results in code injection. Attacking locally is a requirement. Upgrading to version 13.54 is recommended to address this issue. The patch is identified as 5a8b6b6ead12b39e3f32f978a4efd0233facbb01. It is suggested to upgrade the affected component. The fix in the source code mentions: "[J]ust to be safe, probably never happen".
References
- vuldb.com/vuln/360421 (opens in a new tab)
- vuldb.com/vuln/360421/cti (opens in a new tab)
- vuldb.com/submit/800049 (opens in a new tab)
- youtu.be/WktMPapQxlM (opens in a new tab)
- github.com/exiftool/exiftool/commit/5a8b6b6ead12b39e3f32f978a4efd0233facbb01 (opens in a new tab)
- github.com/exiftool/exiftool/commit/5a8b6b6ead12b39e3f32f978a4efd0233facbb01 (opens in a new tab)
- github.com/exiftool/exiftool/releases/tag/13.54 (opens in a new tab)
- github.com/exiftool/exiftool/ (opens in a new tab)