GitLabApplication
CVE-2020-10976
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 · uneditedGitLab EE/CE 8.17 to 12.9 is vulnerable to information leakage when querying a merge request widget.
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 · moderate confidenceGitLab EE/CE versions 8.17 through 12.9 contain an information leakage vulnerability in the merge request widget component. The vulnerability allows unauthorized access to sensitive information when querying the merge request widget, likely due to improper access control or authorization checks in the widget's data retrieval mechanism.
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
>= 8.17.0, <= 12.9CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check GitLab version in the UINavigate to the Admin Area (admin dashboard) and look for the GitLab version displayed on the overview page or in Help > Version. Note the exact version number.Affected if The displayed version is between 8.17.0 and 12.9.0 (inclusive)
-
Check GitLab version via command lineRun the command `sudo gitlab-rake gitlab:env:info` on the GitLab server. Locate the GitLab version in the output.Affected if The version output shows a release between 8.17.0 and 12.9.0 inclusive
-
Confirm merge request functionality is in useVerify that the GitLab instance has merge request features enabled and accessible. Check if projects have existing merge requests or if the merge request module is active in the web interface.Affected if Merge requests can be created or viewed on this GitLab instance
-
Verify version is below patched releaseCompare your installed version number against the fixed version 12.9.1. Any version 12.9.0 or earlier within the 8.17.0 to 12.9.0 range is affected.Affected if Your version is 12.9.0 or earlier, or any version starting at 8.17.0 up to and including 12.9.0
You are affected if your GitLab installation version falls between 8.17.0 and 12.9.0 inclusive and the merge request widget feature is accessible on your instance.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade GitLab to version 12.9.1 or later. This is a standard patch release that addresses the information disclosure in the merge request widget functionality.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10976 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-10976 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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