GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.2 that under certain conditions could have allowed an… (CVE-2026-16627)
A vulnerability in GitLab CE/EE versions from 19.2 up to but not including 19.2.2 allows an authenticated user with developer-role permissions to escalate privileges. This occurs due to improper sanitization of HTML content rendered in a CI job modal, leading to a cross-site scripting (XSS) issue. The vulnerability has been assigned CVE-2026-16627 and is rated with a high severity score of 7.7. GitLab has remediated this issue in version 19.2.2.
AI Analysis
Technical Summary
CVE-2026-16627 is a cross-site scripting vulnerability in GitLab CE/EE affecting all versions starting from 19.2 before 19.2.2. Under certain conditions, an authenticated user with developer-role permissions could exploit improper sanitization of HTML content rendered in a CI job modal to escalate privileges. This vulnerability is categorized under CWE-79 and has a CVSS v3.1 score of 7.7 (AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N), indicating network attack vector, high attack complexity, low privileges required, user interaction needed, scope changed, and high impact on confidentiality and integrity without affecting availability. The issue has been fixed in GitLab version 19.2.2.
Potential Impact
An authenticated developer-role user could exploit this vulnerability to escalate privileges within the GitLab instance by leveraging improper HTML sanitization in CI job modals. This could lead to significant confidentiality and integrity impacts, such as unauthorized access or modification of data. Availability is not affected. There are no known exploits in the wild at this time.
Mitigation Recommendations
GitLab has remediated this vulnerability in version 19.2.2. Users should upgrade to GitLab CE/EE 19.2.2 or later to address this issue. Since this is an on-premises product, administrators must apply the update manually. No additional mitigation steps are indicated by the vendor advisory.
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.2 that under certain conditions could have allowed an… (CVE-2026-16627)
Description
A vulnerability in GitLab CE/EE versions from 19.2 up to but not including 19.2.2 allows an authenticated user with developer-role permissions to escalate privileges. This occurs due to improper sanitization of HTML content rendered in a CI job modal, leading to a cross-site scripting (XSS) issue. The vulnerability has been assigned CVE-2026-16627 and is rated with a high severity score of 7.7. GitLab has remediated this issue in version 19.2.2.
CVSS v3.1
Score 7.7high
Affected software
pkg:github/gitlab-org/gitlabRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-16627 is a cross-site scripting vulnerability in GitLab CE/EE affecting all versions starting from 19.2 before 19.2.2. Under certain conditions, an authenticated user with developer-role permissions could exploit improper sanitization of HTML content rendered in a CI job modal to escalate privileges. This vulnerability is categorized under CWE-79 and has a CVSS v3.1 score of 7.7 (AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N), indicating network attack vector, high attack complexity, low privileges required, user interaction needed, scope changed, and high impact on confidentiality and integrity without affecting availability. The issue has been fixed in GitLab version 19.2.2.
Potential Impact
An authenticated developer-role user could exploit this vulnerability to escalate privileges within the GitLab instance by leveraging improper HTML sanitization in CI job modals. This could lead to significant confidentiality and integrity impacts, such as unauthorized access or modification of data. Availability is not affected. There are no known exploits in the wild at this time.
Mitigation Recommendations
GitLab has remediated this vulnerability in version 19.2.2. Users should upgrade to GitLab CE/EE 19.2.2 or later to address this issue. Since this is an on-premises product, administrators must apply the update manually. No additional mitigation steps are indicated by the vendor advisory.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-mjv5-423q-gjfg
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-16627"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a7cd3e6bf8831d539180258
Added to database: 08/12/2026, 20:13:26 UTC
Last enriched: 08/12/2026, 20:56:36 UTC
Last updated: 08/12/2026, 22:01:17 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.