CVE-2021-22229Public exploitNetwork attack vector

Repository disclosure via uncopied fork visibility settings

Published Jul 6, 2021 · Updated Aug 3, 2024

Improper access control in affected GitLab CE/EE releases starting with 12.8 allows remote authenticated users to disclose repository data by forking. The fork workflow copies the source project's public visibility but not its members-only repository access setting, so the fork exposes the repository to everyone. The source project must be public with repository access limited to project members, and a member must create a fork; the resulting disclosure is read-only.

CVSS severity5.9
Medium
EPSS probability1.08%
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

Improper access control in affected GitLab CE/EE releases starting with 12.8 allows remote authenticated users to disclose repository data by forking. The fork workflow copies the source project's public visibility but not its members-only repository access setting, so the fork exposes the repository to everyone. The source project must be public with repository access limited to project members, and a member must create a fork; the resulting disclosure is read-only.

The record

CVE
CVE-2021-22229
Published
Jul 6, 2021
Updated
Aug 3, 2024
Vendor
GitLab
Product
GitLab
Classifications
T1213.003
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 6, 2021CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 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=>=12.8, <13.11.6
  2. Affected versionversion=>=13.12, <13.12.6
  3. Affected versionversion=>=14.0, <14.0.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=>=12.8, <13.11.6; version=>=13.12, <13.12.6; version=>=14.0, <14.0.2

Published CVSS scores

4.3NIST NVDAV:N/AC:M/Au:N/C:P/I:N/A:N
5.9GitLab Inc.CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
7.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/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

T1213.003Code 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