CI/CD variable disclosure via fork configuration processing
Published Sep 29, 2023 · Updated Nov 20, 2025
Information disclosure in GitLab CE/EE 13.11 through 16.2.7, 16.3 through 16.3.4, and 16.4.0 lets remote authenticated users read CI/CD variables. Gitlab::Ci::YamlProcessor processes an attacker-controlled fork configuration and fetches external includes with unprotected variables in scope. Exploitation requires a public-project fork and a victim project member to visit a crafted blob, CI editor, or new-pipeline page.
Summary
What happened
Information disclosure in GitLab CE/EE 13.11 through 16.2.7, 16.3 through 16.3.4, and 16.4.0 lets remote authenticated users read CI/CD variables. Gitlab::Ci::YamlProcessor processes an attacker-controlled fork configuration and fetches external includes with unprotected variables in scope. Exploitation requires a public-project fork and a victim project member to visit a crafted blob, CI editor, or new-pipeline page.
The record
- CVE
- CVE-2023-0989
- Published
- Sep 29, 2023
- Updated
- Nov 20, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-282, T1566.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 29, 2023CVE publishedPublication date reported by the CVE source.
- Nov 20, 2025Record 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.
- Affected versionversion=0 <16.2.8
- Affected versionversion=16.3 <16.3.5
- Affected versionversion=16.4 <16.4.1
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
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