Skip to content
Server Security Center
KEVcritical10.0 Used in ransomware campaigns

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

GitLab Community and Enterprise Editions · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.

CVSS v3.1 (CVE record)
10.0
critical
EPSS (exploit probability, 30 days)
99.7%
among the highest 0.1% of all CVEs
Added to CISA KEV
2021-11-03
US federal due date 2021-11-17
Ubuntu priority
medium

CVE-2021-22205 explained

CVE-2021-22205 is a remote command execution flaw in GitLab CE/EE affecting all versions starting from 11.9. GitLab did not properly validate image files passed to a file parser. It is listed in the CISA Known Exploited Vulnerabilities catalog with known ransomware use, so exposed instances face real-world risk.

Impact

An unauthenticated attacker can reach the flaw over the network with low complexity and no user interaction. Successful exploitation leads to remote command execution, with high impact on confidentiality, integrity and availability. The scope is changed, so the compromise can extend beyond the GitLab component itself. CISA reports known use in ransomware campaigns.

Who is affected

The gitlab source package in Ubuntu 16.04 LTS is listed as affected. No fixed version has been published for this release in the standard archive. Ubuntu 16.04 LTS is end of life, so administrators should not expect a fix through this channel. Upstream, the issue affects GitLab CE/EE versions starting from 11.9.

Written with AI from the data on this page and checked against it automatically.

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.

CISA required action: Apply updates per vendor instructions.

CISA notes

Upstream versions (CVE record)

From the CVE record published by the vendor or CVE numbering authority.

  • GitLab
    Affected
    • 11.9
    • < 13.8.8
    • 13.9
    • < 13.9.6
    • 13.10
    • < 13.10.3
    Fixed in
    not stated

Ubuntu and Debian releases

A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.

What to do

  1. Identify all systems running GitLab, including the gitlab package on Ubuntu 16.04 LTS.
  2. Upgrade Ubuntu 16.04 LTS systems to a supported Ubuntu release.
  3. Apply GitLab updates per the vendor instructions, as CISA requires for this known exploited vulnerability.
  4. Restart GitLab services after updating so the fixed code is running.
  5. Review affected hosts for signs of compromise, given known ransomware use.

Ubuntu 16.04 LTS is end of life and has no fixed gitlab package. Plan an upgrade to a supported release or a vendor-supported GitLab installation. Until then, remove the instance from public networks, restrict access to trusted users and addresses, and consider taking it offline if it is exposed.

Written with AI from the data on this page and checked against it automatically.

Check and fix on a server

Run on each Ubuntu or Debian server. Replace gitlab with the source package from the table above.

1. Show installed packages built from the source package, with their versions

dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="gitlab"'

No fixed version available

No Ubuntu or Debian release has published a fixed version of gitlab yet, so every installed version is affected. Until a fix is published:

  • Apply the mitigation from the vendor's or your distribution's advisory (see References below).
  • If the server does not need the package, remove it, or replace it with a maintained alternative.
  • Restrict exposure: keep the affected service off the internet, limit access with a firewall or VPN, and turn off the vulnerable feature where you can.

This page updates automatically when Ubuntu or Debian publish a fix.

Ubuntu 16.04 LTS has reached end of life and no longer gets regular security fixes – upgrade to a supported release.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

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

Questions about CVE-2021-22205

Is CVE-2021-22205 being exploited?
Yes. CISA added it to the Known Exploited Vulnerabilities catalog on 2021-11-03 and reports known ransomware use.
Does an attacker need an account?
No. The CVSS vector shows no privileges and no user interaction are required, and the attack works over the network.
Will Ubuntu 16.04 LTS receive a fixed gitlab package?
No fixed version is published, and the release is end of life. Upgrade to a supported release or follow the vendor's update instructions instead of waiting.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.