GitLabApplication
CVE-2020-26413
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 · uneditedAn issue has been discovered in GitLab CE/EE affecting all versions starting from 13.4 before 13.6.2. Information disclosure via GraphQL results in user email being unexpectedly visible.
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 CE/EE versions 13.4 through 13.6.1 contain an information disclosure vulnerability in the GraphQL API that unexpectedly exposes user email addresses to unauthorized parties. This flaw stems from insufficient access control checks in the GraphQL query handling, allowing authenticated or potentially unauthenticated users to query for email addresses they should not have access to.
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.4.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.
-
Check installed GitLab versionNavigate to Admin Area > Applications (or /admin/application_settings) or run `gitlab-rake gitlab:env:info` to view the installed version numberAffected if Version is 13.4.0, 13.4.1, 13.4.2, 13.4.3, 13.4.4, 13.5.0, 13.5.1, 13.5.2, 13.6.0, or 13.6.1 (any version >=13.4.0 and <13.6.2)
-
Confirm GraphQL API is accessibleAttempt to access the GraphQL endpoint at /api/graphql or /api/graphql/v1 (may be accessible without authentication depending on configuration)Affected if GraphQL endpoint responds to requests (any HTTP response other than 404 or connection refused)
-
Verify user email enumeration is possibleSend a GraphQL query requesting user email addresses (e.g., query { users { edges { node { email } } } }) to the /api/graphql endpointAffected if Query returns email addresses for users without proper authorization (response contains email addresses that the requesting user should not have access to)
If GitLab version is 13.4.0 through 13.6.1 AND the GraphQL API is accessible and returns unauthorized email addresses, the environment is affected by this CVE.
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.6.2
Upgrade GitLab to version 13.6.2 or later to receive the vendor patch. Alternatively, restrict GraphQL API access or monitor for unauthorized email enumeration attempts until the upgrade can be performed.
Fix this in GitLab
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26413 — 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-26413 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