LiveActive security incident?Get immediate response
CVE Record

CVE-2020-26406: Certain SAST CiConfiguration information could be viewed by unauthorized users in GitLab EE starting with 1...

Certain 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.

MediumCVSS 5.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This GitLab EE flaw could let people who should not see certain SAST CI configuration details view them through GraphQL. It is an information disclosure issue, not a code execution or outage vulnerability. Business urgency is highest for organizations running old GitLab EE 13.3 to 13.5 versions with sensitive CI security-scanning configuration.

Executive priority

Handle during normal vulnerability remediation unless the affected GitLab instance hosts sensitive security-scanning configuration or many external guest users. Prioritize faster if old GitLab EE versions remain internet-accessible or project visibility settings match the affected scenarios.

Technical view

CVE-2020-26406 affects GitLab EE versions >=13.3,<13.3.9, >=13.4,<13.4.5, and >=13.5,<13.5.2. Certain SAST CiConfiguration information was exposed through GraphQL to non-members of public projects with restricted repository visibility and guest members on private projects. CVSS 3.1 is 5.3, reflecting network access and low confidentiality impact.

Likely exposure

Exposure is likely limited to legacy GitLab EE deployments in the affected version ranges. Relevant cases include public projects with repository visibility restricted, or private projects where guest users exist. Organizations on current supported GitLab versions are unlikely to be exposed to this specific CVE.

Exploitation context

The source bundle does not identify active exploitation, and the CVE is not listed as KEV. The issue is remotely reachable through GraphQL according to the CVE description, but available evidence supports information disclosure only, not integrity compromise, availability impact, or direct code execution.

Researcher notes

The key validation question is not generic GitLab exposure, but whether the instance is GitLab EE in the affected ranges and has the specific visibility and membership conditions. The source bundle does not provide CWE mapping, detailed exploit mechanics, or evidence of exploitation in the wild.

Mitigation direction

  • Upgrade affected GitLab EE instances beyond the listed vulnerable version ranges.
  • Use GitLab vendor guidance when selecting the target supported release.
  • Review project visibility and guest access for sensitive private projects.
  • Limit guest access where SAST configuration details are operationally sensitive.
  • Treat exposed SAST configuration as potentially disclosed until reviewed.

Validation and detection

  • Inventory all GitLab EE instances and record exact versions.
  • Flag versions >=13.3,<13.3.9, >=13.4,<13.4.5, or >=13.5,<13.5.2.
  • Identify public projects with restricted repository visibility.
  • Identify private projects that include guest members.
  • Confirm remediation through authorized access-control testing after upgrade.
Prepared
Confidence
high
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-26406 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2020-26406Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GitLabGitLab EE>=13.3, <13.3.9, >=13.4, <13.4.5, >=13.5, <13.5.2Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.