CVE-2021-22205: Unauthenticated Remote Code Execution in GitLab Image Parsing
- Vendor
- GitLab
CVE-2021-22205 is an unauthenticated remote code execution vulnerability in GitLab Community Edition and Enterprise Edition, introduced in version 11.9. GitLab insufficiently validates uploaded image files before passing them to its ExifTool-based parser. Crafted input containing a backslash followed by a newline can bypass validation and reach dynamic code evaluation, allowing attacker-controlled code or commands to execute. Historical fixes were released in GitLab 13.8.8, 13.9.6, and 13.10.3. The vulnerability has been exploited in ransomware, botnet, cryptomining, and other intrusion campaigns.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation compromises confidentiality, integrity, and availability within the permissions and isolation boundaries of the affected GitLab process. Attackers can execute commands, access or modify accessible application data and credentials, deploy malware or backdoors, and disrupt services. Observed exploitation has enabled ransomware deployment, botnet enrollment, cryptomining, and proxyjacking. Further privilege escalation or lateral movement depends on additional weaknesses or credentials available in the compromised environment; root access is not an inherent outcome.
Mitigation
If you can’t patch tonight, do this now.
Until an upgrade is completed, restrict network access to the GitLab instance to trusted clients through firewall rules, segmentation, or a controlled VPN. Because exploitation does not require authentication, stronger account authentication alone does not prevent it. Apply least privilege and workload isolation to limit consequences, and monitor GitLab-associated processes for unexpected shell execution, payload downloads, unauthorized remote-access tools, and anomalous outbound traffic. These measures reduce exposure or impact but do not correct the parser vulnerability.
Remediation
Patch, then assume compromise.
Upgrade GitLab CE or EE to a currently supported, patched release. Historical releases addressing this vulnerability are 13.8.8, 13.9.6, and 13.10.3 for their respective branches. For potentially compromised installations, patching alone is insufficient: isolate affected systems, preserve evidence, investigate persistence and lateral movement, remove unauthorized access, and rotate exposed credentials and keys.
Exploits
15 exploits validated by Mallory's analysis. Hidden: 1 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2021-22205 exploited in the wild?
- Yes. As of Nov 7, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Nov 3, 2021.
- Is there a public exploit for CVE-2021-22205?
- Yes. Mallory tracks 15 public exploits or proofs of concept for CVE-2021-22205, the earliest disclosed Apr 14, 2021.
- Is there a patch for CVE-2021-22205?
- Upgrade GitLab CE or EE to a currently supported, patched release. Historical releases addressing this vulnerability are 13.8.8, 13.9.6, and 13.10.3 for their respective branches.
- What products are affected by CVE-2021-22205?
- Gitlab.
- How severe is CVE-2021-22205?
- CVE-2021-22205 has a CVSS v3.1 score of 10.0 (Critical) and an EPSS score of 99.7% (100th percentile) as of Nov 7, 2026.
Recent activity
49 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.