CVE-2020-13277Public exploitNetwork attack vector

Private repository disclosure via mirror-triggered impersonation

Published Jun 19, 2020 · Updated Aug 4, 2024

Incorrect authorization in affected GitLab releases 10.6 through 13.0.5 allows remote authenticated users to read private repositories via pull mirrors. When a pull-mirror owner deletes the account, GitLab reassigns mirror-triggered pipelines to another group owner and runs attacker-controlled CI configuration with that owner's CI_JOB_TOKEN. The attacker needs authenticated accounts, a pull mirror configured to trigger pipelines, and a victim group owner; the resulting token reads repositories and registry content accessible to that victim.

CVSS severity6.3
Medium
EPSS probability1.85%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect authorization in affected GitLab releases 10.6 through 13.0.5 allows remote authenticated users to read private repositories via pull mirrors. When a pull-mirror owner deletes the account, GitLab reassigns mirror-triggered pipelines to another group owner and runs attacker-controlled CI configuration with that owner's CI_JOB_TOKEN. The attacker needs authenticated accounts, a pull mirror configured to trigger pipelines, and a victim group owner; the resulting token reads repositories and registry content accessible to that victim.

The record

CVE
CVE-2020-13277
Published
Jun 19, 2020
Updated
Aug 4, 2024
Vendor
GitLab
Product
GitLab
Classifications
CWE-863, T1213.003
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 19, 2020CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>=10.6, <12.9.10
  2. Affected versionversion=>=12.10, <12.10.11
  3. Affected versionversion=>=13.0, <13.0.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=>=10.6, <12.9.10; version=>=12.10, <12.10.11; version=>=13.0, <13.0.6

Published CVSS scores

6.3GitLab Inc.CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
6.5NIST National Vulnerability DatabaseCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-863Incorrect Authorization
T1213.003Data from Information Repositories: Code Repositories

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo