CVE-2021-39869 Information disclosure in GitLab
GitLab project exports may leak trigger tokens, allowing attackers to potentially trigger pipelines or access project resources.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2021-39869?
CVE-2021-39869 is a medium-severity vulnerability in Gitlab Gitlab, published on 5 Oct 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
In all versions of GitLab CE/EE since version 8.9, project exports may expose trigger tokens configured on that project.
Which versions are affected by CVE-2021-39869?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 8.9.0 | 14.1.7, 14.2.5, 14.3.1 |
Products include Gitlab Gitlab.
How do I fix CVE-2021-39869?
Upgrade gitlab to a fixed version for your release line: 14.1.7, 14.2.5 or 14.3.1.
Is CVE-2021-39869 being exploited?
There is no known exploitation of CVE-2021-39869 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2021-39869, GHSA-vj39-w82r-gvcp, UBUNTU-CVE-2021-39869.