GitLab CE/EE ExifTool Remote Code Execution
An improper-validation vulnerability in GitLab Community Edition and Enterprise Edition allows an unauthenticated attacker to achieve remote code execution by uploading a crafted image file processed through a vulnerable ExifTool image-metadata parser.
- Vendor
- GitLab
- Product
- GitLab CE/EE
- CVSS
- 9.9
- EPSS (exploit probability)
- 99.7%
- Status
- kevransomware use
- CISA patch-by (BOD 22-01)
- Published
Is CVE-2021-22205 being exploited?
Yes. CISA added CVE-2021-22205 to its Known Exploited Vulnerabilities catalog on . CISA only lists a CVE when it has reliable evidence of exploitation in the wild. CISA marks it as known to be used in ransomware campaigns.
FIRST's EPSS model puts the probability of exploitation activity in the next 30 days at 99.7% (scored October 14, 2026).
- CISA KEV[ LISTED ]
- ENISA EUVD (exploited)[ — ]
- CIRCL KEV[ — ]
Catalog snapshot 2026-11-17. Full cross-catalog view: /kev-comparison
CVE-2021-22205 timeline
Every event links to its source. Catalog dates are each catalog's own; day offsets count from NVD publication. Data: JSON
What to do
US federal civilian agencies must remediate by (14 days after listing) under BOD 22-01. Everyone else: that deadline is a sensible upper bound, not a target. Vendor guidance and the NVD record are linked under Source above.
CVE-2021-22205 is a critical remote-code-execution vulnerability in GitLab Community Edition and Enterprise Edition, originally patched in April 2021 but not widely recognized as pre-authentication remote code execution until researchers re-analyzed and demonstrated full exploitation in late 2021 — at which point exploitation in the wild began at scale. The flaw sits in GitLab’s handling of uploaded image files: a crafted image processed through a vulnerable bundled ExifTool library could trigger code execution on the GitLab server, reachable by any unauthenticated user able to reach an image-upload endpoint.
Why it mattered
GitLab instances host an organization’s source code, CI/CD pipeline configuration, and often embedded secrets and deployment credentials — a compromise is rarely contained to “just” the Git server. Because the original April 2021 patch notes didn’t clearly convey the severity of unauthenticated pre-auth RCE, a large number of GitLab instances remained unpatched for months; once public proof-of-concept exploit code circulated in late 2021, mass scanning and exploitation of internet-exposed GitLab servers followed, with attackers using compromised instances for cryptomining and further network pivoting.
CISA added the CVE to its KEV catalog in late 2021 once active exploitation was confirmed at scale, well after the original patch had shipped — a reminder that patch availability and patch adoption are not the same thing. Full technical detail and patch guidance are in GitLab’s security release notes and at the NVD link above.
Other GitLab CE/EE CVEs we track
| CVE / Vulnerability | Severity | CVSS | EPSS | Added to KEV |
|---|---|---|---|---|
| CVE-2026-97229 GitLab CI/CD regex integer overflow enables unauthenticated RCEwrite-up | [ CRITICAL ] | 10.0 | 69.3% | |
| CVE-2026-110264 Integer overflow in Onigmo regex engine allows unauthenticated RCEwrite-up | [ CRITICAL ] | 10.0 | 1.3% | — |
| CVE-2026-85706 GitLab Path Traversal Allows Unauthenticated File Readwrite-up | [ CRITICAL ] | 10.0 | 97.4% | |
| CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control Vulnerability | [ CRITICAL ] | 10.0 | 94.5% |
