← Vulnerabilities

CVE-2026-0723

Allows attackers to bypass two-factor authentication in GitLab

An unchecked return value flaw in GitLab CE/EE lets an attacker who knows a victim's credential ID bypass two-factor authentication. The vulnerability affects GitLab versions from 18.6 through 18.8, and is fixed in versions 18.6.4, 18.7.2, and 18.8.2. News reports indicate that GitLab servers are being actively targeted with remote code execution attacks, and CISA has warned about exploitation of a GitLab flaw.

GitLab · Updated 2 Nov · From the public records

Being exploitedNot reportedNo attacks reported in the records
CISA known exploitedNot listedThe US list of flaws under attack
SeverityhighCVSS 7.4 of 10
FixAvailableFixed versions below

Am I affected?

If you run a version older than the fixed one for your line, yes.

Version lineFixed in
GitLab 18.818.8.2
GitLab 18.718.7.2
GitLab 18.618.6.4

What to do

  1. Upgrade to GitLab 18.8.2, 18.7.2, or 18.6.4 depending on your release version.
  2. Rotate all user credentials as a precaution.
  3. Monitor your GitLab servers for any unusual activity.
  4. Follow advisories from GitLab and security authorities for further guidance.

What happened

  1. 30 OctCISA says a max severity GitLab flaw is now exploited in the wild.
  2. 2 NovBleepingComputer reports over 1,000 GitLab servers are vulnerable to ongoing RCE attacks.

The record

CVEWhat it isSeverityCISA listedExploit chance, 30 days
CVE-2026-0723Unchecked Return Value in GitLabhigh 7.4No1.0%
Is anything you run affected?Connect Zotpaper to Claude, ChatGPT or Cursor and ask. It checks your project's packages against this vulnerability and every other one in the advisory databases, and says what to update. Your first 20 lookups are free.
Try it free