CISA Warns of Exploited GitLab Community and Enterprise SSRF Vulnerability
The Cybersecurity and Infrastructure Security Agency (CISA) has identified a critical server-side request forgery (SSRF) vulnerability affecting GitLab Community and Enterprise Editions. This vulnerability is now included in CISA's Known Exploited…
The Cybersecurity and Infrastructure Security Agency (CISA) has identified a critical server-side request forgery (SSRF) vulnerability affecting GitLab Community and Enterprise Editions. This vulnerability is now included in CISA's Known Exploited Vulnerabilities (KEV) catalog.
The vulnerability, tracked as CVE-2021-39935, affects GitLab's CI Lint API. It allows unauthorized external attackers to perform server-side requests without authentication. This can enable threat actors to manipulate the server into making requests to internal resources, potentially exposing sensitive data or facilitating lateral movement within compromised networks.
CVE ID: CVE-2021-39935 Vulnerability Type: Server-Side Request Forgery (SSRF) Related CWE: CWE-918 Affected Products: GitLab Community and Enterprise Editions
This vulnerability is particularly hazardous as it bypasses traditional perimeter defenses, allowing attackers to use the vulnerable GitLab instance as a proxy to access internal systems, cloud metadata services, or other restricted resources.
This vulnerability is now included in CISA's Known Exploited Vulnerabilities (KEV) catalog.
Organizations using affected versions face significant risks, including unauthorized access to internal infrastructure, data exfiltration, and potential supply chain compromises through CI/CD pipeline manipulation.
CISA has issued a remediation timeline for federal agencies under Binding Operational Directive 22-01. Federal Civilian Executive Branch (FCEB) agencies must apply vendor-provided patches or implement mitigations by February 24, 2026. Organizations that cannot patch their systems are advised to discontinue use of the product until security updates become available.
GitLab has released patches to address this vulnerability. Administrators should upgrade to the latest patched versions and review CI Lint API configurations for any suspicious activity. Organizations using cloud-hosted GitLab services should follow BOD 22-01 guidance for cloud service security.
Security teams are advised to audit access logs for indicators of compromise, such as unusual API requests to the CI Lint endpoint and unexpected internal network connections originating from GitLab servers.
Based on reporting by GBHackers.
