CVE-2025-12073 | Server-Side Request Forgery (SSRF) in GitLab

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.0 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions, could have allowed an authenticated user to perform server-side request forgery against internal services by bypassing protections in the Git repository import functionality.

Published: 2026-02-11 Last update: 2026-02-13 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-12073 is rated Low Risk (17.8/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.01%). Mandatory action: Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-12073

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-11 0.01%

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-12073

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 1.4 [email protected]

Weakness enumeration for CVE-2025-12073

OS Trackers for CVE-2025-12073

vendor priority summary link
debian unimportant CVE-2025-12073 unimportant priority: Debian including 1 source packages (gitlab), 1 status rows across 1 suites (sid): resolved 1. https://security-tracker.debian.org/tracker/CVE-2025-12073
ubuntu medium CVE-2025-12073 medium priority: Ubuntu including 2 source packages (gitlab, gitlab-agent), 9 status rows across 5 suites (jammy, noble, questing, upstream, xenial): DNE 4, needs-triage 4, ignored 1. https://ubuntu.com/security/CVE-2025-12073

Affected software / configurations for CVE-2025-12073

Vendor Product Version Raw CPE
gitlab gitlab >= 18.0.0, < 18.6.6 cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*
gitlab gitlab >= 18.0.0, < 18.6.6 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
gitlab gitlab >= 18.7.0, < 18.7.4 cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*
gitlab gitlab >= 18.7.0, < 18.7.4 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
gitlab gitlab >= 18.8.0, < 18.8.4 cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*
gitlab gitlab >= 18.8.0, < 18.8.4 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*

References for CVE-2025-12073

cvelogic Threat Intelligence