# GitLab CI Lint API SSRF — CVE-2021-39935 Patch Bypass, CISA KEV Feb 2026, Cloud Metadata Theft, Internal Service Enumeration, 4-Year Exploitation Gap on Self-Managed Instances

> GitLab CE/EE CI Lint API Server-Side Request Forgery (SSRF) vulnerability (CVE-2021-39935) allows unauthenticated external users to perform server-side requests, enabling access to internal services, cloud metadata endpoints, and credential harvesting. Added to CISA KEV on 2026-02-03 due to confirmed exploitation in the wild.

- **Published:** 2026-02-03T12:00:00Z
- **Last reviewed:** 2026-02-03T12:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-0089
- **Card image:** https://intel.threadlinqs.com/og/threat/threat-intel-gitlab-ci-lint-ssrf-tl-2026-0089.webp?v=dd56dbf5 (Threadlinqs threat intel: CVE-2021-39935 GitLab SSRF: Exploitation Status & Fix (TL-2026-0089) — High severity, 25 IOCs, 9 detection rules.)
- **ID:** TL-2026-0089
- **Severity:** HIGH (CVSS 7.5)
- **Category:** VULNERABILITY
- **Status:** MONITORING
- **Detections:** 9 (1 shown free below) · **IOCs:** 25 (1 shown free below)
- **CVEs:** CVE-2021-39935

## Description

CVE-2021-39935 is a Server-Side Request Forgery (SSRF) vulnerability in GitLab Community Edition (CE) and Enterprise Edition (EE) affecting all versions from 10.5 through 14.5.1. The vulnerability exists in the CI Lint API endpoint, which validates CI/CD pipeline configuration (`.gitlab-ci.yml` files). Unauthorized external users can craft malicious CI configuration payloads that cause the GitLab server to make arbitrary HTTP requests to internal services, cloud provider metadata endpoints (169.254.169.254), and other restricted network resources.

The vulnerability is a patch bypass — an earlier SSRF in the CI Lint API was reported via HackerOne (report #1110131) and patched, but the fix was incomplete. Security researcher @minhli discovered that the access control enforcement could be circumvented in specific configurations. When GitLab instances have sign-ups enabled with the 'New users set to external' option, newly registered external users — who should have no project access and cannot trigger CI pipelines — can still abuse the CI Lint API to perform SSRF attacks without any project membership.

The CI Lint API (`/api/v4/ci/lint`) is designed to validate CI/CD YAML configuration before pipeline execution. The SSRF occurs because the validation process follows `include:` directives that reference remote URLs, allowing an attacker to specify arbitrary internal URLs. This enables:

1. **Cloud metadata theft**: Accessing AWS IMDSv1 (http://169.254.169.254/latest/meta-data/), GCP metadata, and Azure IMDS endpoints to steal IAM credentials, service account tokens, and instance identity documents
2. **Internal service enumeration**: Probing internal network services (Redis, PostgreSQL, Elasticsearch, Consul, Vault) for service discovery and data exfiltration
3. **Credential harvesting**: Accessing internal GitLab services (Gitaly, Workhorse, Rails console) that may expose tokens, API keys, or database credentials
4. **Network reconnaissance**: Mapping internal network topology by observing response timing and error messages from internal hosts

GitLab serves over 30 million registered users and is widely deployed as self-managed instances in enterprise environments, government agencies, and critical infrastructure organizations. Self-managed GitLab instances are particularly vulnerable because they often run within corporate networks with access to sensitive internal services. CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2026-02-03, indicating confirmed exploitation in the wild more than 4 years after the original patch was released — suggesting that many self-managed instances remain unpatched.

The vulnerability was patched in GitLab versions 14.5.2, 14.4.4, and 14.3.6, released on 2021-12-06. GitLab.com (the SaaS offering) was patched immediately. However, self-managed instances require manual upgrades, and the long tail of unpatched GitLab deployments represents significant ongoing risk. The current stable GitLab version is 18.8.4 (released 2026-02-10), meaning vulnerable instances are more than 3 years behind on patches.

The CISA KEV addition 4+ years post-patch highlights a critical pattern: legacy vulnerabilities in widely-deployed DevOps infrastructure continue to be actively exploited by threat actors who scan for unpatched self-managed instances. This mirrors the exploitation lifecycle of CVE-2021-22205 (GitLab Workhorse RCE, KEV since 2021-11-03) and CVE-2023-7028 (GitLab password reset takeover, KEV since 2024-05-01), confirming GitLab as a high-value target for persistent exploitation campaigns.

## MITRE ATT&CK

- T1595 Active Scanning
- T1190 Exploit Public-Facing Application
- T1552 Unsecured Credentials
- T1528 Steal Application Access Token
- T1016 System Network Configuration Discovery
- T1046 Network Service Discovery
- T1580 Cloud Infrastructure Discovery
- T1018 Remote System Discovery
- T1082 System Information Discovery
- T1213 Data from Information Repositories
- T1210 Exploitation of Remote Services
- T1211 Exploitation for Stealth
- T1567 Exfiltration Over Web Service
- T1199 Trusted Relationship
- T1588 Obtain Capabilities
- T1078 Valid Accounts
- T1606 Forge Web Credentials
- T1530 Data from Cloud Storage
- T1552.005 Cloud Instance Metadata API
- T1552.001 Credentials In Files
- T1213.003 Code Repositories
- T1548 Abuse Elevation Control Mechanism
- T1078.004 Cloud Accounts
- T1526 Cloud Service Discovery

## Free detection (Splunk SPL)

**GitLab Server Outbound Connection to Internal Services — SSRF Service Probing** (`TL-2026-0089-SPL-003`)

Detects GitLab application server making HTTP connections to internal services that should not be directly accessed: Redis (6379), HashiCorp Vault (8200), Consul (8500), Prometheus (9090), Elasticsearch (9200), and GitLab internal services (Docker Registry 5000, Pages 8060, Workhorse 8080). CVE-2021-39935 SSRF allows attackers to proxy requests through GitLab to these internal services for data theft, credential harvesting, and infrastructure mapping. Any GitLab-to-internal-service connection outside the expected allowlist is an exploitation indicator.

- **Language:** Splunk SPL
- **ATT&CK:** T1046, T1016, T1018
- **Data sources:** firewall_logs, network_flow
- **Severity:** high
- **Confidence:** high

### Splunk SPL

```spl
index=firewall OR index=network sourcetype=firewall
| search src_ip IN ("gitlab_server_ip_1", "gitlab_server_ip_2")
| search dest_port IN (6379, 8200, 8500, 9090, 9200, 5000, 8060, 8080)
| eval target_service=case(
  dest_port=6379, "Redis — cache poisoning, session theft risk",
  dest_port=8200, "HashiCorp Vault — secret extraction risk (API keys, DB creds, certificates)",
  dest_port=8500, "Consul — complete infrastructure mapping (all registered services)",
  dest_port=9090, "Prometheus — metrics exposure, potential secrets in labels",
  dest_port=9200, "Elasticsearch — log data access, PII exposure",
  dest_port=5000, "Docker Registry — container image enumeration, secrets in layers",
  dest_port=8060, "GitLab Pages — internal service access",
  dest_port=8080, "GitLab Workhorse — internal proxy access",
  1=1, "Unknown internal service"
)
| eval expected=case(
  dest_ip IN ("expected_redis_ip") AND dest_port=6379, "EXPECTED",
  dest_ip IN ("expected_pg_ip") AND dest_port=5432, "EXPECTED",
  1=1, "UNEXPECTED"
)
| where expected="UNEXPECTED"
| stats count as connections, values(target_service) as services_probed, dc(dest_ip) as unique_targets, values(dest_ip) as target_ips, earliest(_time) as first_probe, latest(_time) as last_probe by src_ip
| eval risk=case(
  unique_targets > 5, "CRITICAL — Systematic internal service enumeration via SSRF (" . unique_targets . " unique targets)",
  unique_targets > 2, "HIGH — Multiple internal services probed (" . unique_targets . " targets)",
  1=1, "MEDIUM — Unexpected internal service connection"
)
| sort -unique_targets
```

**Known false positives:**

- GitLab's expected connections to its own Redis and PostgreSQL (must be allowlisted)
- Monitoring systems that probe GitLab internal ports for health checks

**Tuning notes:** Create an allowlist of GitLab's expected internal connections (Redis, PostgreSQL, Gitaly) and alert on everything else. Replace placeholder IPs with actual infrastructure IPs. Multiple unexpected targets in a short window = systematic SSRF probing. Network segmentation preventing GitLab from reaching non-essential internal services is the strongest defense.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- GitLab CI Lint API High-Volume Requests — SSRF Reconnaissance (locked: unlock with TL Creds)
- GitLab Process Connecting to Cloud Metadata Endpoint — Defender for Endpoint (locked: unlock with TL Creds)
- Stolen IAM Credential Usage from Non-GitLab Infrastructure — CloudTrail Detection (locked: unlock with TL Creds)
- GitLab CI Lint API Request with Internal IP Include Directive — CVE-2021-39935 SSRF (locked: unlock with TL Creds)
- GitLab Vulnerable Version Detection — CVE-2021-39935 Compliance Check (locked: unlock with TL Creds)
- GitLab SSRF Response Pattern — Error Messages Leaking Internal Service Information (locked: unlock with TL Creds)
- GitLab CI Lint API Unauthenticated Access Anomaly — CVE-2021-39935 SSRF (locked: unlock with TL Creds)
- GitLab Server Outbound Connection to Cloud Metadata Endpoint — SSRF Credential Theft (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sample indicators (1 of 25)

Defanged, TLP:CLEAR.

- URL: `hxxp://metadata[.]google[.]internal/computeMetadata/v1/`

Full set of 25 indicators unlocks with TL Creds: https://threadlinqs.com/tl-creds

## Sources

- [GitLab Security Release: 14.5.2, 14.4.4, 14.3.6](https://about.gitlab.com/releases/2021/12/06/security-release-gitlab-14-5-2-released/)
- [CISA KEV — CVE-2021-39935 GitLab CI Lint API SSRF](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-39935)
- [NVD — CVE-2021-39935 (CVSS 7.5 High)](https://nvd.nist.gov/vuln/detail/CVE-2021-39935)
- [GitLab Issue #346187 — SSRF patch for CI Lint API is incomplete](https://gitlab.com/gitlab-org/gitlab/-/issues/346187)
- [HackerOne Report #1236965 — CI Lint API SSRF Bypass by @minhli](https://hackerone.com/reports/1236965)
- [AttackerKB — CVE-2021-39935 Assessment](https://attackerkb.com/topics/rBNJsr82mk/cve-2021-39935)
- [MITRE CVE Record — CVE-2021-39935](https://www.cve.org/CVERecord?id=CVE-2021-39935)
- [GitLab CVE JSON — CVE-2021-39935](https://gitlab.com/gitlab-org/cves/-/blob/master/2021/CVE-2021-39935.json)
- [GitLab Patch Release 18.8.4 — Contains 2 additional SSRF fixes](https://about.gitlab.com/releases/2026/02/10/patch-release-gitlab-18-8-4-released/)
- [CISA Known Exploited Vulnerabilities Catalog — Full GitLab Entries](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?search_api_fulltext=gitlab)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-0089
