What is the CVSS score of CVE-2026-13320?

CVE-2026-13320 has a CVSS 3.1 base score of 5.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.3%.

Which versions of GitLab are affected by CVE-2026-13320?

GitLab CE/EE versions 15.7 through 19.1.1 contain a stored/reflected cross-site scripting vulnerability that allows authenticated users to inject and execute arbitrary JavaScript in other users'…. A patch is available.

How to fix or mitigate CVE-2026-13320?

Within 24 hours: Identify all GitLab CE/EE instances and confirm affected versions (15.7 before 18.11.7, 19.0 before 19.0.4, 19.1 before 19.1.2). Within 7 days: Upgrade to GitLab CE/EE 18.11.7, 19.0.4, 19.1.2 or later. Within 30 days: Review audit logs and commit history for the vulnerability exposure window; audit user access patterns for signs of session hijacking or unauthorized actions.

GitLab CVE-2026-13320

EUVD-2026-42402 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-07-08 cve@gitlab.com

GHSA-m49f-rvv4-r4rv

XSS Gitlab Red Hat

5.4

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.4 MEDIUM

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

vuln.today AI

7.7 HIGH

Network-reachable authenticated XSS needing only a content-creation privilege (PR:L, not H), specific conditions (AC:H) and victim viewing (UI:R); executes in another user's context (S:C) with high C/I impact, no availability effect.

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

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

Red Hat

7.3 HIGH

qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Severity Changed

Jul 09, 2026 - 20:37 NVD

HIGH MEDIUM

CVSS changed

Jul 09, 2026 - 20:37 NVD

7.3 (HIGH) 5.4 (MEDIUM)

Patch available

Jul 08, 2026 - 22:04 EUVD

Analysis Generated

Jul 08, 2026 - 21:33 vuln.today

DescriptionNVD

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.7 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user to execute arbitrary scripts in another user's browser session due to improper sanitization of user-supplied input.

AnalysisAI

Stored/reflected cross-site scripting in GitLab CE/EE (all versions from 15.7 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2) lets an authenticated user inject unsanitized input that executes arbitrary JavaScript in a victim's browser session, enabling session hijacking or actions on the victim's behalf. The scope-changed CVSS 7.3 reflects that the payload crosses a security boundary into another user's context. There is no public exploit identified at time of analysis, though the flaw originated from a HackerOne bug bounty submission and vendor patches are already available.

Technical ContextAI

GitLab is a self-managed and SaaS DevOps platform (Community and Enterprise Editions) built on Ruby on Rails with a Vue/JavaScript front end that renders large volumes of user-supplied content (issues, merge requests, comments, project metadata, work items). The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), where user-supplied input is not correctly sanitized or contextually encoded before being rendered in another user's browser DOM, allowing HTML/JavaScript injection. No CPE strings were supplied in the intelligence, so exact affected-configuration enumeration relies on the vendor-stated version ranges rather than NVD CPE data. The linked work item (gitlab-org/gitlab#604063) corresponds to the internal remediation tracking.

RemediationAI

Vendor-released patch: upgrade to GitLab CE/EE 18.11.7, 19.0.4, or 19.1.2 (whichever is on your release branch), per the GitLab patch release advisory (https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-1-2-released/); self-managed operators should apply the patch release immediately and GitLab.com is already remediated. If patching cannot be performed at once, reduce exposure by restricting who can create or edit the content types that carry the payload (limit project/group membership and untrusted external collaborators), enforcing that only trusted users have the elevated privileges the vector requires, and monitoring for anomalous script-like input in user-generated fields; note these controls reduce collaboration flexibility and do not fully close the injection path, so they are stopgaps only until the upgrade is applied.