CVE-2021-22178Network attack vector

Authenticated SSRF via Prometheus URL validation bypass

Published Mar 24, 2021 · Updated Aug 3, 2024

Server-side request forgery in GitLab 13.2 and later allows remote authenticated users to make GitLab request attacker-chosen network resources through the Prometheus integration. The integration validates a user-supplied API URL before connection, but DNS rebinding or related validation and connection timing lets the resolved destination change to an internal address after the check. A Maintainer-level project user must configure the integration; the bounded impact is unauthorized network access and possible disclosure of reachable internal service responses, without demonstrated integrity or availability impact.

CVSS severity5.0
Medium
EPSS probability1.11%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Server-side request forgery in GitLab 13.2 and later allows remote authenticated users to make GitLab request attacker-chosen network resources through the Prometheus integration. The integration validates a user-supplied API URL before connection, but DNS rebinding or related validation and connection timing lets the resolved destination change to an internal address after the check. A Maintainer-level project user must configure the integration; the bounded impact is unauthorized network access and possible disclosure of reachable internal service responses, without demonstrated integrity or availability impact.

The record

CVE
CVE-2021-22178
Published
Mar 24, 2021
Updated
Aug 3, 2024
Vendor
GitLab
Product
GitLab
Classifications
CWE-918, T1190
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Mar 24, 2021CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>=13.2, <13.6.7
  2. Affected versionversion=>=13.7, <13.7.7
  3. Affected versionversion=>=13.8, <13.8.4

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=>=13.2, <13.6.7; version=>=13.7, <13.7.7; version=>=13.8, <13.8.4

Published CVSS scores

5.0GitLab CNACVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-918Server-Side Request Forgery (SSRF)
T1190Exploit Public-Facing Application

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo