Skip to main content

GitLab CVE-2026-10712

| EUVDEUVD-2026-39171 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-06-25 cve@gitlab.com GHSA-93jf-78vf-79px
6.1
CVSS 3.1 · NVD
Share

Severity by source

Vendor (gitlab) PRIMARY
HIGH
qualitative
NVD
6.1 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
vuln.today AI
8.0 HIGH

Network-delivered XSS needing victim interaction and conditional preconditions gives AV:N/AC:H/UI:R; attacker unauthenticated (PR:N); script in trusted origin changes scope (S:C) with high C/I and no availability impact.

3.1 AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N
4.0 AV:N/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (gitlab).

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

5
Severity Changed
Jun 26, 2026 - 18:37 NVD
HIGH MEDIUM
CVSS changed
Jun 26, 2026 - 18:37 NVD
8.0 (HIGH) 6.1 (MEDIUM)
Patch available
Jun 25, 2026 - 07:01 EUVD
Analysis Generated
Jun 25, 2026 - 05:31 vuln.today
CVE Published
Jun 25, 2026 - 05:16 cve.org
HIGH 8.0

DescriptionNVD

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.10 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an unauthenticated user to execute arbitrary JavaScript in a user's browser session due to improper path validation under certain conditions.

AnalysisAI

Cross-site scripting in GitLab CE/EE (18.10 through 18.11.5, 19.0 through 19.0.2, and 19.1.0) lets an unauthenticated attacker run arbitrary JavaScript in a victim's authenticated browser session by abusing improper path validation, but only under specific conditions and after a logged-in user interacts with attacker-controlled content. The CVSS 8.0 rating (scope-changed, high confidentiality and integrity impact) reflects that successful exploitation effectively hijacks the victim's GitLab session. No public exploit has been identified at time of analysis and the issue is not in CISA KEV, though a HackerOne report exists and GitLab shipped fixes in 18.11.6, 19.0.3, and 19.1.1.

Technical ContextAI

GitLab is a self-managed and SaaS DevOps platform (Git hosting, CI/CD, issue tracking) built as a large Ruby on Rails application with a heavily JavaScript-driven frontend. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), here reached via improper path validation: a route or resource path is not correctly canonicalized or sanitized before being reflected into the DOM, letting attacker-controlled data escape into an executable script context. Because the injected script runs inside the trusted GitLab origin, it inherits the victim's authenticated session, which is why the CVSS scope is Changed (S:C) - the vulnerable web component compromises the separate browser security context. Exact affected CPEs are not enumerated in the provided NVD data beyond the version ranges in the description.

RemediationAI

Upgrade to a fixed release: GitLab CE/EE 18.11.6, 19.0.3, or 19.1.1 (or later) depending on your branch - Vendor-released patches: 18.11.6 / 19.0.3 / 19.1.1, per https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-1-1-released/. Self-managed administrators should apply the patch release immediately, since GitLab.com is already remediated. If upgrading cannot be scheduled at once, reduce exposure by restricting network access to the GitLab web interface (VPN/IP allowlist) so untrusted users cannot deliver malicious links to authenticated staff, and reinforce a strict Content-Security-Policy to limit inline-script execution where supported - note that custom CSP changes can break legitimate GitLab UI features and integrations and must be tested. Advising users not to click untrusted GitLab links is a weak compensating control given UI:R is the only interaction barrier; patching is the only reliable fix. Track remediation via the work item at https://gitlab.com/gitlab-org/gitlab/-/work_items/601857.

More in Gitlab

View all
CVE-2021-22205 CRITICAL POC
10.0 Apr 23

An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. Rated critical severity (CVSS 10

CVE-2023-7028 CRITICAL POC
10.0 Jan 12

An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, 16.

CVE-2026-85706 CRITICAL POC
10.0 Sep 12

Unauthenticated arbitrary file read in GitLab CE/EE lets remote attackers retrieve files from the GitLab server via the

CVE-2013-4490 MEDIUM POC
6.5 May 13

The SSH key upload feature (lib/gitlab_keys.rb) in gitlab-shell before 1.7.3, as used in GitLab 5.0 before 5.4.1 and 6.x

CVE-2022-2992 CRITICAL POC
9.9 Oct 17

A vulnerability in GitLab CE/EE affecting all versions from 11.10 prior to 15.1.6, 15.2 to 15.2.4, 15.3 to 15.3.2 allows

CVE-2026-87719 CRITICAL POC
9.9 Sep 12

Sensitive credential and configuration disclosure in GitLab Enterprise Edition allows an authenticated user with Duo Cha

CVE-2018-18843 CRITICAL POC
10.0 Dec 04

The Kubernetes integration in GitLab Enterprise Edition 11.x before 11.2.8, 11.3.x before 11.3.9, and 11.4.x before 11.4

CVE-2024-45409 CRITICAL POC
9.8 Sep 10

The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t

CVE-2022-1162 CRITICAL POC
9.8 Apr 04

A hardcoded password was set for accounts registered using an OmniAuth provider (e.g. Rated critical severity (CVSS 9.8)

CVE-2022-0735 CRITICAL POC
9.8 Mar 28

An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.10 before 14.6.5, all versions star

CVE-2021-22175 CRITICAL POC
9.8 Jun 11

When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab af

CVE-2021-22203 CRITICAL POC
9.8 Apr 02

An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7.9 before 13.8.7, all versions sta

Share

CVE-2026-10712 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy