dbcve.org
GitLabApplication

CVE-2026-1516

MEDIUM · 5.7 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to 18.8.9 / 18.9.5 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable

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 EE affecting all versions from 18.0.0 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that in Code Quality reports could have allowed an authenticated user to leak IP addresses of users viewing the report via specially crafted content.

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 an information disclosure vulnerability in GitLab's Code Quality reporting feature. An authenticated attacker could embed specially crafted content in Code Quality reports that, when viewed by other users, would leak those users' IP addresses to the attacker.

MitigationUpgrade GitLab EE to version 18.8.9, 18.9.5, 18.10.3 or later. Alternatively, restrict access to Code Quality reports until the upgrade can be performed.

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:>= 18.0.0, < 18.8.9>= 18.9.0, < 18.9.5>= 18.10.0, < 18.10.3

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/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. Check the installed GitLab version
    Navigate to Admin Area > Overview > Dashboard, or use the help page (click the question mark icon and select 'Help' or 'Version'), or run `gitlab-rake gitlab:env:info` in the console. Look for the version number in the format 18.x.y.
    Affected if The version is 18.0.0 or higher but lower than 18.8.9, OR 18.9.0 or higher but lower than 18.9.5, OR 18.10.0 or higher but lower than 18.10.3.
  2. Verify if Code Quality reports are being used
    Check if any projects have Code Quality reports enabled. In the GitLab UI, go to a project's Settings > CI/CD > General pipelines, or check the project's merge requests for Code Quality report artifacts. Alternatively, search the GitLab database: `SELECT project_id FROM ci_reports WHERE report_type = 'code_quality' LIMIT 10;` or list files in the artifacts storage directory.
    Affected if Any project has generated or is storing Code Quality reports (typically as JSON artifacts from CI/CD pipelines).
  3. Check for Code Quality report artifacts in pipelines
    Navigate to a project's CI/CD > Pipelines and look for recent pipeline runs. Check if any have 'Code Quality' as a job name. Or use the API: `GET /api/v4/projects/:id/pipelines` and check for code_quality jobs, or check the artifacts storage under /var/opt/gitlab/gitlab-rails/shared/artifact_storage/.
    Affected if Any pipeline jobs named 'code_quality' have run and produced artifacts.
  4. Inspect Code Quality report file storage
    If you have server access, locate the Code Quality report files. These are typically stored as `artifacts/code_quality/report.json` within project storage. Check the GitLab Rails logs for requests to `/projects/-/jobs/artifacts/*/file/artifacts/code_quality/*` or similar paths.
    Affected if Code Quality report JSON files exist in the system and have been accessed by users through the GitLab interface.

You are affected if your GitLab version falls within the vulnerable ranges AND you have projects that generate or display Code Quality reports, as the IP leakage occurs when users view these reports.

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.8.9 / 18.9.5 / 18.10.3 or later
Fixed in 18.8.918.9.518.10.3
Interim mitigation

Upgrade GitLab EE to version 18.8.9, 18.9.5, 18.10.3 or later. Alternatively, restrict access to Code Quality reports until the upgrade can be performed.

Recommended fix High confidence

GitLab 18.10.3 or later (or 18.8.9+/18.9.5+ depending on your branch)

  1. 1. Back up your current GitLab installation and database
  2. 2. Identify your current GitLab version using `gitlab-rake gitlab:env:info`
  3. 3. For GitLab 18.0.0 through 18.8.x: upgrade to version 18.8.9 or later
  4. 4. For GitLab 18.9.x: upgrade to version 18.9.5 or later
  5. 5. For GitLab 18.10.x: upgrade to version 18.10.3 or later
  6. 6. After upgrade, verify the instance is running using `gitlab-rake gitlab:check`
  7. 7. Test Code Quality report functionality to ensure the fix is working
Caveat Review GitLab 18.10 release notes for any breaking changes between your current version and target version, as major version upgrades may include schema changes requiring downtime

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

Fix this in GitLab Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1516 — 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-1516 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