dbcve.org
GitLabApplication

CVE-2026-13320

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 18.11.7 / 19.0.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 5d ago

Surfaced from public web coverage — external links open in a new tab.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in GitLab where an authenticated user can inject malicious scripts through improper sanitization of user-supplied input. The payload gets stored and executes in another user's browser session when they view the affected content, allowing session hijacking or data theft.

MitigationUpgrade GitLab to version 18.11.7, 19.0.4, or 19.1.2 or later. Review and audit recent user-generated content for malicious scripts that may have been injected during the vulnerable period.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 15.7.0, < 18.11.7>= 19.0.0, < 19.0.4>= 19.1.0, < 19.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed GitLab version
    Run command: gitlab-rake gitlab:env:info or check /opt/gitlab/embedded/service/gitlab-rails/VERSION file
    Affected if Version cannot be determined or command fails
  2. Compare version against first affected range
    Parse the version number and check if it falls within >= 15.7.0 AND < 18.11.7
    Affected if Version is 15.7.0 through 18.11.6 inclusive
  3. Compare version against second affected range
    Parse the version number and check if it falls within >= 19.0.0 AND < 19.0.4
    Affected if Version is 19.0.0 through 19.0.3 inclusive
  4. Compare version against third affected range
    Parse the version number and check if it falls within >= 19.1.0 AND < 19.1.2
    Affected if Version is 19.1.0 through 19.1.1 inclusive
  5. Verify authentication and user input features
    Confirm that GitLab user authentication is enabled and user-generated content features (such as issues, merge requests, comments, or wikis) are accessible to authenticated users
    Affected if User authentication is disabled or no user-generated content features are in use

Environment is affected if the installed GitLab version falls within any of the three vulnerable ranges (15.7.0 to 18.11.6, 19.0.0 to 19.0.3, or 19.1.0 to 19.1.1) and authenticated users can create or modify content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 18.11.7 / 19.0.4 / 19.1.2 or later
Fixed in 18.11.719.0.419.1.2
Interim mitigation

Upgrade GitLab to version 18.11.7, 19.0.4, or 19.1.2 or later. Review and audit recent user-generated content for malicious scripts that may have been injected during the vulnerable period.

Recommended fix High confidence

18.11.7 (or 19.0.4 / 19.1.2 depending on your upgrade path - 18.11.7 is recommended for most users)

  1. 1. Back up your GitLab instance data and configuration before proceeding with the upgrade.
  2. 2. Identify your current GitLab version by navigating to the GitLab Admin area or running `sudo gitlab-rake gitlab:env:info`.
  3. 3. If your current version is >= 15.7.0 and < 18.11.7: Plan an upgrade to version 18.11.7 or later.
  4. 4. If your current version is >= 19.0.0 and < 19.0.4: Plan an upgrade to version 19.0.4 or later.
  5. 5. If your current version is >= 19.1.0 and < 19.1.2: Plan an upgrade to version 19.1.2 or later.
  6. 6. Review the GitLab upgrade documentation for your installation method (omnibus, source, or Helm chart) at docs.gitlab.com/ee/update/.
  7. 7. Execute the upgrade following the documented upgrade path for your specific installation.
  8. 8. After upgrade, verify the new version is running and test that the XSS vulnerability is no longer present.
Caveat Check GitLab release notes for your target version for any breaking changes or required manual migrations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-13320 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13320 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data