# CVE-2021-43113: Command injection in itext7-core

> Attackers can execute arbitrary commands via malicious filenames in iText PDF library due to improper handling in Ghostscript integration.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Dec 2021
- **Updated:** 25 Feb 2026
- **Also known as:** DEBIAN-CVE-2021-43113, DLA-3273-1, DSA-5323-1, GHSA-gv87-q66h-4277, UBUNTU-CVE-2021-43113, openSUSE-SU-2024:11980-1

## What is CVE-2021-43113?

CVE-2021-43113 is a critical command injection vulnerability in Debian Debian Linux, published on 15 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

iTextPDF in iText 7 and up to (excluding 4.4.13.3) 7.1.17 allows command injection via a CompareTool filename that is mishandled on the gs (aka Ghostscript) command line in GhostscriptHelper.java.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

4 open source packages ship an affected version, including com.itextpdf:itext7-core and com.itextpdf:itextpdf. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.itextpdf:itext7-core` | Maven | All versions | 7.1.17 |
| `com.itextpdf:itext7-core` | Maven | All versions | 7.1.17 |
| `com.itextpdf:itextpdf` | Maven | All versions | 5.5.13.3 |
| `com.itextpdf:itextpdf` | Maven | All versions | 5.5.13.3 |

Products: Debian Debian Linux, Itextpdf Itext.

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

Upgrade com.itextpdf:itext7-core to 7.1.17 or later.

## Is CVE-2021-43113 being exploited?

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

## 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-43113 and fix it if it is affected.

What it is: CVE-2021-43113 is a critical command injection vulnerability in Debian Debian Linux, published on 15 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-43113 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.itextpdf:itext7-core (Maven): affected all versions; fixed in 7.1.17
- com.itextpdf:itext7-core (Maven): affected all versions; fixed in 7.1.17
- com.itextpdf:itextpdf (Maven): affected all versions; fixed in 5.5.13.3
- com.itextpdf:itextpdf (Maven): affected all versions; fixed in 5.5.13.3

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-43113/ (Markdown: https://insights.sbomify.com/CVE-2021-43113/index.md)
```

## Sources

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

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