CVE-2026-4363
Authorization Bypass via Improper Caching in GitLab EE
Publication date: 2026-03-25
Last updated on: 2026-03-26
Assigner: GitLab Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gitlab | gitlab | From 18.1.0 (inc) to 18.8.7 (exc) |
| gitlab | gitlab | From 18.9.0 (inc) to 18.9.3 (exc) |
| gitlab | gitlab | 18.10.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-863 | The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in GitLab EE allows an authenticated user to gain unauthorized access to resources due to improper caching of authorization decisions, which impacts confidentiality and integrity of data.
Such unauthorized access could potentially lead to non-compliance with common standards and regulations like GDPR and HIPAA, which require strict controls over access to sensitive data to protect privacy and ensure data integrity.
Therefore, if exploited, this vulnerability might result in violations of these regulations by exposing protected information or allowing unauthorized modifications.
Upgrading to the patched versions is strongly advised to mitigate these risks and maintain compliance.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability affects GitLab Enterprise Edition (EE) versions from 18.1 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1. Detection primarily involves identifying if your GitLab instance is running one of these vulnerable versions.
You can check the GitLab version installed on your system by running the following command on the GitLab server:
- sudo gitlab-rake gitlab:env:info
Alternatively, if you have access to the GitLab web interface, the version is usually displayed in the footer or under the Admin Area > Overview > System Information.
If your version is within the vulnerable range, it is recommended to upgrade immediately to the patched versions (18.8.7, 18.9.3, or 18.10.1 and later) to mitigate the risk.
There are no specific network detection commands or signatures provided for this vulnerability, as it is related to improper caching of authorization decisions within the application.
Can you explain this vulnerability to me?
This vulnerability in GitLab EE affects versions from 18.1 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1. Under certain conditions, it could allow an authenticated user to gain unauthorized access to resources. The issue arises due to improper caching of authorization decisions, which means that the system might incorrectly grant access based on cached permissions rather than current authorization checks.
How can this vulnerability impact me? :
The impact of this vulnerability is that an authenticated user could potentially access resources they are not authorized to view or modify. This unauthorized access could lead to exposure of sensitive information or unauthorized actions within the GitLab environment. However, the CVSS score of 3.7 indicates a low to moderate severity, suggesting that exploitation requires certain conditions and may have limited impact.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update GitLab EE to a fixed version. Specifically, upgrade to version 18.8.7 or later if you are on the 18.8 branch, 18.9.3 or later if on the 18.9 branch, or 18.10.1 or later if on the 18.10 branch.