CVE-2026-0723

HIGHNVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-01-22. NVD baseline CVSS 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.4
EG Score
7.4(medium)
EPSS
53.2%
KEV
Not listed

Published

January 22, 2026

Last Modified

January 26, 2026

References (3)

Vendor Advisories for CVE-2026-0723(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 02:30 UTCEPSS rescore
  4. 2026-07-05 02:30 UTCEPSS rescore
  5. 2026-07-04 06:31 UTCEPSS rescore
  6. 2026-07-01 15:06 UTCEPSS rescore
  7. 2026-07-01 15:06 UTCEPSS rescore
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-29 14:06 UTCEPSS rescore
  10. 2026-06-28 14:07 UTCEPSS rescore
  11. 2026-06-28 04:56 UTCEPSS rescore
  12. 2026-06-28 04:56 UTCEPSS rescore
  13. 2026-06-27 03:08 UTCEPSS rescore
  14. 2026-06-25 18:16 UTCOSV refresh
  15. 2026-06-25 13:49 UTCEPSS rescore
  16. 2026-06-24 14:05 UTCEPSS rescore
  17. 2026-06-23 21:32 UTCEPSS rescore
  18. 2026-06-22 14:25 UTCEPSS rescore
  19. 2026-06-22 14:25 UTCEPSS rescore
  20. 2026-06-21 14:56 UTCEPSS rescore
  21. 2026-06-21 14:56 UTCEPSS rescore
  22. 2026-06-21 01:59 UTCEPSS rescore
  23. 2026-06-21 01:59 UTCEPSS rescore
  24. 2026-06-19 19:25 UTCEPSS rescore
  25. 2026-06-18 17:52 UTCEPSS rescore
Show 39 more
  1. 2026-06-17 17:53 UTCEPSS rescore
  2. 2026-06-16 17:52 UTCEPSS rescore
  3. 2026-06-15 17:48 UTCEPSS rescore
  4. 2026-06-14 23:18 UTCEPSS rescore
  5. 2026-06-13 23:00 UTCEPSS rescore
  6. 2026-06-13 23:00 UTCEPSS rescore
  7. 2026-06-12 23:12 UTCEPSS rescore
  8. 2026-06-11 14:00 UTCEPSS rescore
  9. 2026-06-10 22:18 UTCEPSS rescore
  10. 2026-06-10 13:22 UTCEPSS rescore
  11. 2026-06-08 14:17 UTCEPSS rescore
  12. 2026-06-08 14:17 UTCEPSS rescore
  13. 2026-06-08 07:51 UTCEG score recompute
  14. 2026-06-08 07:51 UTCGHSA enrichment
  15. 2026-06-07 15:25 UTCEPSS rescore
  16. 2026-06-07 15:24 UTCEPSS rescore
  17. 2026-06-06 13:47 UTCEPSS rescore
  18. 2026-06-06 13:47 UTCEPSS rescore
  19. 2026-06-06 13:47 UTCEPSS rescore
  20. 2026-06-05 22:47 UTCEPSS rescore
  21. 2026-06-05 06:10 UTCEPSS rescore
  22. 2026-06-05 06:10 UTCEPSS rescore
  23. 2026-06-04 13:12 UTCEPSS rescore
  24. 2026-06-04 13:12 UTCEPSS rescore
  25. 2026-06-04 13:12 UTCEPSS rescore
  26. 2026-06-02 20:13 UTCEPSS rescore
  27. 2026-06-02 20:13 UTCEPSS rescore
  28. 2026-06-01 13:51 UTCEPSS rescore
  29. 2026-06-01 13:51 UTCEPSS rescore
  30. 2026-06-01 13:51 UTCEPSS rescore
  31. 2026-05-31 22:30 UTCEPSS rescore
  32. 2026-05-31 22:30 UTCEPSS rescore
  33. 2026-05-31 00:16 UTCEPSS rescore
  34. 2026-05-31 00:16 UTCEPSS rescore
  35. 2026-05-31 00:16 UTCEPSS rescore
  36. 2026-05-29 15:25 UTCEG score recompute
  37. 2026-05-29 15:25 UTCGHSA enrichment
  38. 2026-05-29 13:44 UTCEPSS rescore
  39. 2026-05-29 13:44 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-0723?
CVE-2026-0723 is a high vulnerability published on January 22, 2026. 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…
When was CVE-2026-0723 disclosed?
CVE-2026-0723 was first published in the National Vulnerability Database on January 22, 2026, with the most recent update on January 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-0723 actively exploited?
CVE-2026-0723 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 53.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-0723?
CVE-2026-0723 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-0723?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-0723, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-0723

Explore →

Is Your Infrastructure Affected by CVE-2026-0723?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs