EUVD-2026-80222
GHSA-3xqm-9h96-4cr4
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:L
Authoring the payload requires a GitLab account (PR:L), the victim must render it (UI:R), and the attack is conditional (AC:H); impact falls on the victim's session.
Primary rating from Vendor (GitLab).
CVSS VectorVendor: GitLab
Lifecycle Timeline
3DescriptionCVE.org
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.3 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an authenticated user could have induced a targeted user to perform unintended state-changing HTTP requests due to improper sanitization of user-controlled data in the Markdown JSON table renderer.
AnalysisAI
Improper sanitization of user-controlled data in GitLab CE/EE's Markdown JSON table renderer allows crafted content to make a targeted user's browser issue unintended state-changing HTTP requests when the rendered page is viewed, affecting versions from 15.3 through 19.1.7, 19.2.5 and 19.3.1. Exploit details are publicly available through a linked HackerOne report, and the vendor CVSS of 8.2 reflects network reachability, a high attack-complexity rating, required user interaction and a scope change. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires three concrete things: first, the attacker must be able to place attacker-controlled data into a GitLab surface that is rendered as Markdown through the JSON table renderer - issues, comments, merge request descriptions or wikis on a project the victim will view; the description explicitly attributes the payload to a user (an authenticated author), which conflicts with the published PR:N metric and should be verified against the vendor. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The vendor vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:L yields 8.2 High, driven by full confidentiality and integrity impact and a scope change, but tempered by AC:H and UI:R - the attacker must get a targeted, logged-in user to render the malicious content. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Upgrade immediately to GitLab 19.3.2, or to 19.2.6 on the 19.2 line or 19.1.8 on the 19.1 line - these are the vendor-released fixed versions per the official patch release page at https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-2-released/ (work item: https://gitlab.com/gitlab-org/gitlab/-/work_items/621447). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all GitLab CE/EE instances and confirm exact version numbers, then upgrade any instance on 19.1.x to 19.1.8, any on 19.2.x to 19.2.6, and any on 19.3.x to 19.3.2 (vendor-released fixes); if an instance cannot be upgraded immediately, restrict external exposure of the web interface, prioritize upgrades for instances reachable from the internet, and warn users not to open untrusted Markdown content such as tables in issues, merge requests, and comments. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. Rated critical severity (CVSS 10
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.
Unauthenticated arbitrary file read in GitLab CE/EE lets remote attackers retrieve files from the GitLab server via the
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
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
Sensitive credential and configuration disclosure in GitLab Enterprise Edition allows an authenticated user with Duo Cha
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
The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t
A hardcoded password was set for accounts registered using an OmniAuth provider (e.g. Rated critical severity (CVSS 9.8)
An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.10 before 14.6.5, all versions star
When requests to the internal network for webhooks are enabled, a server-side request forgery vulnerability in GitLab af
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.7.9 before 13.8.7, all versions sta
Same weakness CWE-79 – Cross-site Scripting (XSS)
View allShare
External POC / Exploit Code
Leaving vuln.today