GitLabApplication
CVE-2020-26406
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 · uneditedCertain SAST CiConfiguration information could be viewed by unauthorized users in GitLab EE starting with 13.3. This information was exposed through GraphQL to non-members of public projects with repository visibility restricted as well as guest members on private projects. Affected versions are: >=13.3, <13.3.9,>=13.4, <13.4.5,>=13.5, <13.5.2.
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 confidenceGitLab EE 13.3+ exposes SAST CiConfiguration information through GraphQL to unauthorized users. Non-members of public projects with restricted repository visibility and guest members of private projects can view sensitive CI/CD configuration data that should be restricted.
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
>= 13.3.0, < 13.3.9>= 13.4.0, < 13.4.5>= 13.5.0, < 13.5.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.
-
Identify GitLab versionRun `sudo gitlab-rake gitlab:env:info` or check the GitLab admin panel under Help > Version to find the installed GitLab EE version.Affected if The version falls within 13.3.0 to 13.3.8, 13.4.0 to 13.4.4, or 13.5.0 to 13.5.1.
-
Confirm GraphQL API is accessibleVerify the GraphQL endpoint is available at your GitLab instance by accessing /api/graphql or checking that GraphQL is not disabled in the application settings.Affected if GraphQL is enabled (it is enabled by default in affected versions).
-
Identify public projects with restricted repository visibilityIn the GitLab admin panel, search for projects with Public visibility but with restricted repository access settings, or use the API: `GET /projects?visibility=public&repository_access_level=disabled`Affected if Public projects exist where repository access is restricted or disabled.
-
Check for guest users in private projectsReview project membership in private projects to identify users assigned the Guest role, or query via API: `GET /projects/:id/members/all` and look for access_level = 10 (Guest).Affected if Private projects have users with Guest role membership.
You are affected if your GitLab EE version is 13.3.0-13.3.8, 13.4.0-13.4.4, or 13.5.0-13.5.1 AND you have public projects with restricted repository visibility OR private projects with guest members, since these unauthorized users could query the GraphQL API to expose SAST configuration.
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.3.913.4.513.5.2
Upgrade GitLab EE to version 13.3.9, 13.4.5, 13.5.2 or later to patch the authorization bypass in the GraphQL API that allows unauthorized access to SAST configuration.
Fix this in GitLab
Scoped from the published advisory
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26406 — 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-26406 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