CVE-2026-6883

CVE-2026-6883 is a low-severity vulnerability in Gitlab with a CVSS 3.x base score of 2.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-862.

Key facts

Description

GitLab has remediated an issue in GitLab EE affecting all versions from 15.7 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user to bypass merge request approval requirements due to improper cleanup of orphaned policy records.

Frequently asked questions

What is CVE-2026-6883?
GitLab has remediated an issue in GitLab EE affecting all versions from 15.7 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user to bypass merge request approval requirements due to improper cleanup of orphaned policy records.
How severe is CVE-2026-6883?
CVE-2026-6883 has a CVSS 3.x base score of 2.6, rated low severity. It is exploitable over network with high attack complexity, requires low privileges and user interaction. Impact on confidentiality is none, integrity low, and availability none.
Is CVE-2026-6883 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-6883?
CVE-2026-6883 affects Gitlab. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-6883?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-6883 have an EU (EUVD) identifier?
Yes. CVE-2026-6883 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-30237.
When was CVE-2026-6883 published?
CVE-2026-6883 was published on 2026-05-14 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Gitlab

All CVEs affecting Gitlab →

Other CWE-862 (Missing Authorization) vulnerabilities

Browse all CWE-862 (Missing Authorization) vulnerabilities →