Skip to main content
Mallory
LowVulnerability

CVE-2026-122226: GitLab EE Duo Group-Based Access Rule Bypass

Published Nov 17, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 3 in a dayToday
CVSS2.2Low · v3.1
EPSS0.18%8th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-122226CWE-460 · Improper Cleanup on Thrown Exception

CVE-2026-122226 is an improper exception-cleanup vulnerability in GitLab Enterprise Edition affecting versions from 18.8 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6. Under certain conditions, improper handling of failed updates to GitLab Duo group-based access rules allows an authenticated user to access Duo features that those rules restrict. The specific vulnerable function and failure-triggering conditions are not publicly detailed.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation bypasses group-based restrictions on GitLab Duo features, undermining enforcement of configured access policies. The vulnerability has a low integrity impact, with no identified confidentiality or availability impact. Its CVSS v3.1 base score is 2.2 (AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N).

Mitigation

If you can’t patch tonight, do this now.

No temporary workaround has been specified.

Remediation

Patch, then assume compromise.

Upgrade affected self-managed GitLab EE installations to version 19.3.9, 19.4.8, or 19.5.6, as appropriate for the release branch, or a later fixed release. GitLab.com is already patched, and GitLab Dedicated customers require no action.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-122226 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-122226 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-122226?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-122226.
Is there a patch for CVE-2026-122226?
Upgrade affected self-managed GitLab EE installations to version 19.3.9, 19.4.8, or 19.5.6, as appropriate for the release branch, or a later fixed release. GitLab.com is already patched, and GitLab Dedicated customers require no action.
How severe is CVE-2026-122226?
CVE-2026-122226 has a CVSS v3.1 score of 2.2 (Low) and an EPSS score of 0.18% (8th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.