# CVE-2026-7580: Exiftool JPEG/QuickTime/MOV/MP4 GM.pm Process_mrld code injection


- **Severity:** Medium 4.8 (`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:P`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 1 May 2026
- **Updated:** 1 May 2026
- **Also known as:** DEBIAN-CVE-2026-7580, GHSA-qjrf-c4wp-pgxx, OESA-2026-2222, OESA-2026-2223, OESA-2026-2224, UBUNTU-CVE-2026-7580

## What is CVE-2026-7580?

CVE-2026-7580 is a medium-severity vulnerability in Exiftool, published on 1 May 2026. 

### Official 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".

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-7580?


## How do I fix CVE-2026-7580?

Upgrade to a fixed version.

## Is CVE-2026-7580 being exploited?

There is no known exploitation of CVE-2026-7580 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7580 and fix it if it is affected.

What it is: CVE-2026-7580 is a medium-severity vulnerability in Exiftool, published on 1 May 2026. 
Exploitation: There is no known exploitation of CVE-2026-7580 in the wild and no public exploit code.

Affected product: Exiftool. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-7580/ (Markdown: https://insights.sbomify.com/CVE-2026-7580/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-7580
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-7580
- OSV: https://osv.dev/vulnerability/CVE-2026-7580

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-7580/
Summaries are generated and may contain mistakes; the official description above is the record.