CVE-2026-6883

Low
2.6
0.05.010.0
Year
2026
Published
May 14, 2026
Known Affected Devices
0
CVSS Score
2.6

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.

CVSS Vector Breakdown

CVSS 3.1
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N
AV
Attack Vector
Network

Exploitable remotely over the network without requiring access to the local system.

AC
Attack Complexity
High

Exploit requires specific conditions, timing, or configuration to succeed.

PR
Privileges Required
Low

Basic user account required (e.g. standard login without admin rights).

UI
User Interaction
Required

Victim must take an action (e.g. click a link, open a file) for the exploit to succeed.

S
Scope
Unchanged

Exploiting the vulnerability only affects the vulnerable component itself.

C
Confidentiality Impact
None

No confidentiality impact. Sensitive data is not exposed.

I
Integrity Impact
Low

Attacker can modify some data, but scope or consequence is limited.

A
Availability Impact
None

No availability impact. Service remains fully operational.

FAQ

How severe is CVE-2026-6883?

CVE-2026-6883 has a CVSS score of 2.6/10, rated as Low. Review the affected products list and apply vendor patches.

What does the CVSS score mean for CVE-2026-6883?

CVSS (Common Vulnerability Scoring System) rates vulnerability severity from 0.0 to 10.0. CVE-2026-6883 scores 2.6/10 (Low). Scores 9.0–10.0 are Critical, 7.0–8.9 are High, 4.0–6.9 are Medium, and below 4.0 are Low.

Which devices are affected by CVE-2026-6883?

The list of devices confirmed to be affected by CVE-2026-6883 is shown in the "Affected Devices" section above. Check your firmware version against the vendor security advisory and apply the latest patch.

How do I fix or mitigate CVE-2026-6883?

Apply the latest firmware or software update from the vendor. Check the References section above for official advisories and patch notes. If no patch is available, consider disabling the affected feature or isolating the device from untrusted networks.