CVE-2026-122226

Low
2.2
0.05.010.0
Year
2026
Published
Nov 17, 2026
Known Affected Devices
0
CVSS Score
2.2

What is CVE-2026-122226?

GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user to access GitLab Duo features restricted by group-based access rules due to improper handling of failed updates to those rules.

CVSS Vector Breakdown

CVSS 3.1
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/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
High

Administrative or root-level privileges required to exploit.

UI
User Interaction
None

No user interaction required. Exploit runs without any victim action.

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-122226?

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

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

CVSS (Common Vulnerability Scoring System) rates vulnerability severity from 0.0 to 10.0. CVE-2026-122226 scores 2.2/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-122226?

The list of devices confirmed to be affected by CVE-2026-122226 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-122226?

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.