Authenticated pipeline-value disclosure via API authorization bypass
Published Feb 11, 2026 · Updated Feb 11, 2026
Authorization bypass in GitLab CE/EE allows remote authenticated users to view certain pipeline values through the Pipeline Schedules API. GitLab has not published the specific user-controlled key or authorization check that the endpoint handles incorrectly. Exploitation requires authenticated API access and user interaction under unspecified conditions, and the reported consequence is limited to disclosure of pipeline values.
Summary
What happened
Authorization bypass in GitLab CE/EE allows remote authenticated users to view certain pipeline values through the Pipeline Schedules API. GitLab has not published the specific user-controlled key or authorization check that the endpoint handles incorrectly. Exploitation requires authenticated API access and user interaction under unspecified conditions, and the reported consequence is limited to disclosure of pipeline values.
The record
- CVE
- CVE-2025-14594
- Published
- Feb 11, 2026
- Updated
- Feb 11, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-639
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 2026CVE publishedPublication date reported by the CVE source.
- Feb 11, 2026Record 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=17.11 <18.6.6
- Affected versionversion=18.7 <18.7.4
- Affected versionversion=18.8 <18.8.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
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