Actively exploitedKnown ransomware use

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

GitHub Community and Enterprise Editions that utilize the ability to upload images through GitLab Workhorse are vulnerable to remote code execution. Workhorse passes image file extensions through ExifTool, which improperly validates the image files.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch nowCybergen assessment

CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 3 Nov 2021.
CISA lists it as known to be used in ransomware campaigns.
Rated Critical severity (CVSS 10.0, scored by Vendor).
This product type is often exposed to the internet, which is where attackers scan for it first.
It has been in the catalogue for 1,829 days. Systems still unpatched now have almost certainly been scanned for it.

The Vulnerability

What It Is

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.

Affected Versions

Product	Versions
GitLab GitLab	>=11.9, <13.8.8 >=13.9, <13.9.6 >=13.10, <13.10.3

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

1
Find it
Search your asset inventory and external attack surface for GitLab Community and Enterprise Editions. Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management
2
Fix it
Apply updates per vendor instructions.
Vulnerability Management
3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response
4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing

Vendor Advisories

nvd.nist.gov/vuln/detail/CVE-2021-22205

Regulation

The Compliance Clock

Cyber EssentialsRated critical, so if it affects devices in your Cyber Essentials scope, the update must be installed within 14 days of the vendor releasing it.NIS2If exploitation causes a significant incident, essential and important entities owe their CSIRT an early warning within 24 hours and a notification within 72 hours.DORAFinancial entities must classify ICT incidents and send an initial notification for a major incident within strict deadlines, with exploited flaws a common cause.US federal (BOD 22-01)Federal civilian agencies had until 17 Nov 2021 to remediate. A sensible benchmark for everyone else.

General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.

Stay Ahead

More Exploited GitLab Flaws

All 6 exploited GitLab vulnerabilities

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2021-22205 and every other exploited flaw on the list.

Check My Exposure

Evidence

PREVENTION

DETECTION & MITIGATION

GRC

INCIDENT RESPONSE

CLOUD SECURITY

CRITICAL INFRASTRUCTURE

REGULATED SERVICES

PUBLIC SERVICES

COMMERCIAL

THREAT INTELLIGENCE

MANAGED SECURITY

NETWORK & CLOUD

RISK & COMPLIANCE

DATA & APPLICATIONS

PEOPLE & EMAIL

FOR VENDORS

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

Should You Worry?

What It Is

Affected Versions

What To Do Now

Find it

Fix it

Hunt for compromise

Prove it is fixed

Vendor Advisories

The Compliance Clock

More Exploited GitLab Flaws

Not Sure If You Are Exposed?

Sources