# CVE-2021-22205: GitLab Community and Enterprise Editions Remote Code Execution

> Remote attackers can execute arbitrary commands by uploading malicious image files to GitLab, requiring immediate patching.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Apr 2021
- **Updated:** 6 Aug 2026
- **Also known as:** BIT-gitlab-2021-22205, GHSA-vgp2-3hxm-6x85, UBUNTU-CVE-2021-22205

## What is CVE-2021-22205?

CVE-2021-22205 is a critical code injection vulnerability in Gitlab Gitlab, published on 23 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. GitLab was not properly validating image files that were passed to a file parser which resulted in a remote command execution.

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

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

1 open source package ship an affected version, including gitlab. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gitlab` | Bitnami | From 11.9.0 | 13.8.8, 13.9.6, 13.10.3 |

Products: Gitlab Gitlab.

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

Upgrade gitlab to a fixed version for your release line: 13.8.8, 13.9.6 or 13.10.3. US federal agencies must fix it by 17 Nov 2021.

## Is CVE-2021-22205 being exploited?

Yes. Attackers have exploited CVE-2021-22205 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Public exploit code:

- CVE-2021-22205& GitLab CE/EE RCE (github_poc): https://github.com/Al1ex/CVE-2021-22205
- GitLab CE/EE Preauth RCE using ExifTool (github_poc): https://github.com/inspiringz/CVE-2021-22205
- https://github.com/mr-r3bot/Gitlab-CVE-2021-22205 (github_poc): https://github.com/mr-r3bot/Gitlab-CVE-2021-22205
- Pocsuite3 For CVE-2021-22205 (github_poc): https://github.com/XTeam-Wing/CVE-2021-22205
- CVE-2021-22205 Unauthorized RCE (github_poc): https://github.com/r0eXpeR/CVE-2021-22205
- CVE-2021-22205 Gitlab 未授权远程代码执行漏洞 EXP, 移除了对djvumake & djvulibre的依赖，可在win平台使用 (github_poc): https://github.com/whwlsfb/CVE-2021-22205

## Other vulnerabilities in Gitlab Gitlab

- [CVE-2026-97229](https://insights.sbomify.com/CVE-2026-97229/): GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound (critical 10.0, exploited in the wild)
- [CVE-2026-85706](https://insights.sbomify.com/CVE-2026-85706/): GitLab Community Edition and Enterprise Edition Path Traversal (critical 10.0, exploited in the wild)
- [CVE-2023-7028](https://insights.sbomify.com/CVE-2023-7028/): GitLab Community and Enterprise Editions Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2021-39935](https://insights.sbomify.com/CVE-2021-39935/): GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF) (medium 6.8, exploited in the wild)
- [CVE-2021-22175](https://insights.sbomify.com/CVE-2021-22175/): GitLab Server-Side Request Forgery (SSRF) (medium 6.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-22205 is a critical code injection vulnerability in Gitlab Gitlab, published on 23 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2021-22205 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Affected packages and fixed versions:
- gitlab (Bitnami): affected from 11.9.0; fixed in 13.8.8, 13.9.6, 13.10.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-22205/ (Markdown: https://insights.sbomify.com/CVE-2021-22205/index.md)
```

## Sources

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

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