# CVE-2021-22204: ExifTool Remote Code Execution

> Attackers can execute arbitrary code by tricking users into processing a malicious DjVu image with ExifTool.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Yes, since 17 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Apr 2021
- **Updated:** 21 Oct 2025
- **Also known as:** DEBIAN-CVE-2021-22204, DLA-2663-1, DSA-4910-1, GHSA-9377-7hwr-p4w6, MGASA-2021-0259, UBUNTU-CVE-2021-22204, USN-4987-1, USN-4987-2, openSUSE-SU-2021:0707-1

## What is CVE-2021-22204?

CVE-2021-22204 is a medium-severity code injection vulnerability in Debian Debian Linux, published on 23 Apr 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper neutralization of user data in the DjVu file format in ExifTool versions 7.44 and up allows arbitrary code execution when parsing the malicious image

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2021-22204?

It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-Image-ExifTool` | SUSE:Package Hub 15 SP1 | All versions | 12.25-bp152.4.3.1 |
| `perl-Image-ExifTool` | SUSE:Package Hub 15 SP2 | All versions | 12.25-bp152.4.3.1 |
| `perl-Image-ExifTool` | openSUSE:Leap 15.2 | All versions | 12.25-bp152.4.3.1 |

Products: Debian Debian Linux, Exiftool Project Exiftool, Fedoraproject Fedora.

## How do I fix CVE-2021-22204?

Upgrade to a fixed version. US federal agencies must fix it by 1 Dec 2021.

## Is CVE-2021-22204 being exploited?

Yes. Attackers have exploited CVE-2021-22204 in the wild since at least 17 Nov 2021.

Public exploit code:

- Python exploit for the CVE-2021-22204 vulnerability in Exiftool (github_poc): https://github.com/convisolabs/CVE-2021-22204-exiftool
- Exploit for CVE-2021-22204 (ExifTool) - Arbitrary Code Execution (github_poc): https://github.com/UNICORDev/exploit-CVE-2021-22204
- https://github.com/AssassinUKG/CVE-2021-22204 (github_poc): https://github.com/AssassinUKG/CVE-2021-22204
- exiftool arbitrary code execution vulnerability (github_poc): https://github.com/se162xg/CVE-2021-22204
- exiftool exploit (github_poc): https://github.com/mr-tuhin/CVE-2021-22204-exiftool
- POC for exiftool vuln (CVE-2021-22204). (github_poc): https://github.com/bilkoh/POC-CVE-2021-22204

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22204 and fix it if it is affected.

What it is: CVE-2021-22204 is a medium-severity code injection vulnerability in Debian Debian Linux, published on 23 Apr 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2021-22204 in the wild since at least 17 Nov 2021.

Affected product: Debian Debian Linux. 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-2021-22204/ (Markdown: https://insights.sbomify.com/CVE-2021-22204/index.md)
```

## Sources

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

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