Description
GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.4 and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user to read policy configuration belonging to a namespace they were not authorized to access, due to incorrect authorization checks in a GraphQL query.
Published: 2026-08-12
Score: 4.3 Medium
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

An authenticated user with access to GitLab Enterprise Edition can trigger a GraphQL query that bypasses the normal authorization logic, allowing the user to read policy configuration files of a namespace to which the user is not granted permission. This flaw is a classic Authorization Bypass (CWE‑863) that permits data exposure without affecting code execution or availability.

Affected Systems

The vulnerability affects all GitLab Enterprise Edition releases prior to version 19.1.4 and all releases prior to 19.2.2. Only the newer releases address the issue; older releases continue to expose policy data to unauthorized users.

Risk and Exploitability

The CVSS score of 4.3 indicates moderate potential impact. Because the EPSS score is not available, the likelihood of exploitation cannot be quantified, but the vulnerability is not listed in CISA’s KEV catalog. Attackers would need an authenticated account on the affected instance; the flaw does not provide privilege escalation or remote code execution. Nonetheless, any compromised or malicious legitimate account could gain insight into organizational policies, potentially aiding broader attacks. The risk level is therefore moderate, warranting remediation as soon as possible.

Generated by OpenCVE AI on August 12, 2026 at 22:40 UTC.

Remediation

Vendor Solution

Upgrade to versions 19.1.4, 19.2.2 or above.


OpenCVE Recommended Actions

  • Upgrade the GitLab instance to version 19.1.4, 19.2.2 or any newer release that contains the fix.
  • Restrict GraphQL access by configuring role‑based permissions so that only users with explicit policy‑view rights can execute the affected query.
  • Audit logs for unexpected policy‑configuration queries and examine access patterns for anomalous reads.
  • Maintain a regular update cadence for GitLab to avoid future unpatched security concerns.

Generated by OpenCVE AI on August 12, 2026 at 22:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 12 Aug 2026 19:30:00 +0000

Type Values Removed Values Added
Description GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.1.4 and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user to read policy configuration belonging to a namespace they were not authorized to access, due to incorrect authorization checks in a GraphQL query.
Title Incorrect Authorization in GitLab
First Time appeared Gitlab
Gitlab gitlab
Weaknesses CWE-863
CPEs cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
Vendors & Products Gitlab
Gitlab gitlab
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitLab

Published:

Updated: 2026-08-12T19:04:26.420Z

Reserved: 2026-07-30T20:04:25.029Z

Link: CVE-2026-18433

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-12T20:17:41.723

Modified: 2026-08-12T20:17:41.723

Link: CVE-2026-18433

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-12T22:45:10Z

Weaknesses