What is the CVSS score of EUVD-2026-36225?

EUVD-2026-36225 has a CVSS 3.1 base score of 6.5 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

Is there a patch available for EUVD-2026-36225?

Yes, a patch is available for EUVD-2026-36225. Update the affected software to the latest version immediately.

GitLab CE/EE EUVD-2026-36225

| CVE-2026-9204 MEDIUM

Server-Side Request Forgery (SSRF) (CWE-918)

2026-06-11 GitLab

GHSA-c4m8-pv9j-v7mm

Gitlab SSRF

6.5

CVSS 3.1 · NVD

Severity by source

Vendor (GitLab) PRIMARY

MEDIUM

qualitative

NVD

6.5 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

vuln.today AI

6.3 MEDIUM

S:C is warranted because SSRF enabling access to internal network resources and Gitaly backend constitutes impact beyond the vulnerable application's own trust boundary.

3.1 AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N

4.0 AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N

Primary rating from Vendor (GitLab).

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

CVSS changed

Jun 11, 2026 - 17:37 NVD

5.3 (MEDIUM) 6.5 (MEDIUM)

Patch available

Jun 11, 2026 - 13:01 EUVD

Analysis Generated

Jun 11, 2026 - 11:51 vuln.today

DescriptionNVD

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions could have allowed an authenticated user to read arbitrary files from the Gitaly server and access internal network resources during repository import, due to insufficient validation of secondary URLs.

AnalysisAI

Server-Side Request Forgery (SSRF) in GitLab CE/EE's repository import feature allows an authenticated low-privileged user to read arbitrary files from the backend Gitaly server and probe internal network resources by supplying maliciously crafted secondary URLs that bypass input validation. Affected versions span the 18.10, 18.11, and 19.0 release lines, all patched by GitLab on 2026-06-10. No public exploit code and no CISA KEV listing have been identified at time of analysis, though the combination of authentication-only gating and network-accessible entry point makes this a meaningful lateral-movement risk in self-managed GitLab deployments.

Technical ContextAI

CWE-918 (Server-Side Request Forgery) arises when an application fetches a remote resource based on attacker-controlled input without adequately restricting the set of reachable destinations. GitLab's repository import workflow accepts remote repository URLs, including 'secondary URLs' used for credential or redirect handling, and forwards requests from the GitLab application tier to backend services. Gitaly is GitLab's dedicated gRPC-based Git storage backend, running as a privileged internal service with access to repository data on the file system. By injecting file-scheme URIs or internal network addresses into secondary URL parameters during import, an attacker can cause the GitLab application to issue requests on their behalf to Gitaly's file system or to other resources on the internal network segment. The CPE cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:* covers both Community Edition and Enterprise Edition across all platforms. The root cause is insufficient allowlist validation of URL schemes and destination addresses for secondary URLs in the import pipeline.

RemediationAI

The primary fix is upgrading to a patched release: GitLab CE/EE 18.10.8, 18.11.5, or 19.0.2, all released on 2026-06-10 as documented at https://about.gitlab.com/releases/2026/06/10/patch-release-gitlab-19-0-2-released/. Administrators unable to upgrade immediately should consider restricting the repository import feature to trusted roles or disabling it entirely via Admin Area > Settings > General > Import and export settings, which eliminates the attack surface at the cost of blocking legitimate import workflows. In cloud deployments, restricting outbound network egress from the GitLab application tier to only required external IP ranges will limit the usefulness of SSRF for internal network reconnaissance, though it does not prevent Gitaly file access. GitLab.com users require no action. For self-managed instances, monitoring GitLab application logs for anomalous import requests targeting file:// or internal RFC-1918 addresses can serve as a detective control while patch deployment is in progress.