GitLabApplication
CVE-2020-26408
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 · uneditedA limited information disclosure vulnerability exists in Gitlab CE/EE from >= 12.2 to <13.4.7, >=13.5 to <13.5.5, and >=13.6 to <13.6.2 that allows an attacker to view limited information in user's private profile
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 confidenceA broken access control vulnerability in GitLab CE/EE allows authenticated attackers to view limited information from user private profiles that should be restricted. The issue stems from insufficient permission checks on profile data access.
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
>= 12.2.0, < 13.4.7>= 13.5.0, < 13.5.5>= 13.6.0, < 13.6.2CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Determine installed GitLab versionRun command: gitlab-rake gitlab:env:info or check /opt/gitlab/versionAffected if Version is in range >=12.2.0 and <13.4.7, OR >=13.5.0 and <13.5.5, OR >=13.6.0 and <13.6.2
-
Confirm GitLab componentVerify this is GitLab Community Edition (CE) or Enterprise Edition (EE) using gitlab-rake gitlab:env:infoAffected if Component is GitLab CE or EE and version is in affected ranges above
-
Verify authentication configurationCheck if user authentication is enabled and external users exist: examine gitlab.rb/gitlab.yml for auth settings and review active user countAffected if Authentication is enabled with active authenticated users present in the system
-
Assess profile visibility settingsReview whether private profile data could be accessed: check if users have set profile fields to private and if multiple user accounts exist in the instanceAffected if Multiple authenticated users exist and private profile information is present in the system
User is affected if their GitLab installation version falls within any of the three vulnerable ranges (>=12.2.0/<13.4.7, >=13.5.0/<13.5.5, or >=13.6.0/<13.6.2) and has authenticated users with private profile data.
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 data13.4.713.5.513.6.2
Upgrade GitLab to version 13.4.7, 13.5.5, 13.6.2 or later to resolve the broken access control in profile visibility.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26408 — 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-26408 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