Missing Authorization in GitLab (CVE-2026-4879)
A missing authorization vulnerability in GitLab EE versions from 16.0 up to but not including 19.0.6, 19.1 up to 19.1.4, and 19.2 up to 19.2.2 could allow an authenticated user with developer-role permissions to view external status check configurations that should be restricted to higher-privileged roles. This issue affects a merge request API endpoint and has been remediated by GitLab.
AI Analysis
Technical Summary
CVE-2026-4879 is a missing authorization vulnerability in GitLab Enterprise Edition affecting versions >=16.0.0 <19.0.6, >=19.1.0 <19.1.4, and >=19.2.0 <19.2.2. Under certain conditions, an authenticated user with developer-level permissions could access external status check configurations that are intended to be restricted to users with higher privileges. The vulnerability arises due to insufficient authorization checks on a merge request API endpoint. GitLab has issued patches to fix this issue in versions 19.0.6, 19.1.4, and 19.2.2.
Potential Impact
An attacker with developer-role permissions could view sensitive configuration information related to external status checks that should only be accessible to higher-privileged users. This could potentially lead to information disclosure within the affected GitLab instances. There are no known exploits in the wild reported for this vulnerability.
Mitigation Recommendations
GitLab has released official patches that remediate this vulnerability in versions 19.0.6, 19.1.4, and 19.2.2. Users should upgrade affected GitLab EE instances to these versions or later to resolve the issue. Since this is not a cloud service, remediation is the responsibility of the user. No additional mitigations are specified.
Missing Authorization in GitLab (CVE-2026-4879)
Description
A missing authorization vulnerability in GitLab EE versions from 16.0 up to but not including 19.0.6, 19.1 up to 19.1.4, and 19.2 up to 19.2.2 could allow an authenticated user with developer-role permissions to view external status check configurations that should be restricted to higher-privileged roles. This issue affects a merge request API endpoint and has been remediated by GitLab.
Affected software
pkg:bitnami/gitlabRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-4879 is a missing authorization vulnerability in GitLab Enterprise Edition affecting versions >=16.0.0 <19.0.6, >=19.1.0 <19.1.4, and >=19.2.0 <19.2.2. Under certain conditions, an authenticated user with developer-level permissions could access external status check configurations that are intended to be restricted to users with higher privileges. The vulnerability arises due to insufficient authorization checks on a merge request API endpoint. GitLab has issued patches to fix this issue in versions 19.0.6, 19.1.4, and 19.2.2.
Potential Impact
An attacker with developer-role permissions could view sensitive configuration information related to external status checks that should only be accessible to higher-privileged users. This could potentially lead to information disclosure within the affected GitLab instances. There are no known exploits in the wild reported for this vulnerability.
Mitigation Recommendations
GitLab has released official patches that remediate this vulnerability in versions 19.0.6, 19.1.4, and 19.2.2. Users should upgrade affected GitLab EE instances to these versions or later to resolve the issue. Since this is not a cloud service, remediation is the responsibility of the user. No additional mitigations are specified.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BIT-gitlab-2026-4879
- Osv Schema Version
- 1.6.2
- Aliases
- ["CVE-2026-4879"]
- Ecosystems
- ["Bitnami"]
- Database Specific Severity
- Medium
- Cvss Version
- null
Threat ID: 6a8460a2c6e8be033245a859
Added to database: 08/18/2026, 13:39:46 UTC
Last enriched: 08/18/2026, 13:41:52 UTC
Last updated: 08/18/2026, 15:06:23 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.