Skip to main content
Apexward Pulse
Type Vulnerability

GitLab Community Edition and Enterprise Edition

GitLab Patch Release: 16.7.3 16.6.5 16.5.7

1 source

At a glance

Low
Suggested 30-day window, counted from the last update
Evidence-weighted, not popularity
Why Low

Low rather than Medium: Business impact is 20 of 100, little reported harm so far.

Briefing

  • IT leaders should verify if their GitLab deployments are affected by this migration issue and plan upgrades accordingly.

Questions to ask IT

  • Do we run GitLab Community Edition and Enterprise Edition, and which versions?
  • Is any of it reachable from the internet?
  • If it is still not patched, what mitigation is in place, and what is holding the fix up?

Next steps

  1. Confirm whether this affects systems or suppliers in your estate

Summary

  • GitLab released versions 16.7.3, 16.6.5, and 16.5.7 to address an issue with a database migration that prevented upgrades from completing.
  • The updates ensure the chat_names table migration is idempotent across GitLab Community Edition and Enterprise Edition versions 16.7.3, 16.6.5, and 16.5.7.

Read the original reportGitLab security releases(opens in a new tab)

Products and services involved

Pulse

Last change 5d ago · Recheck overdue since 4 Nov 2026, 18:21 UK time

  1. Story3 Nov 2026, 18:21 UK time · 5d ago

    Linked reporting from GitLab security releases (vendor psirt).

    Read source (GitLab security releases)

1 entry so far. The timeline chart appears once this story has more history.

Sources

How we know

Statements extracted from sources. Higher confidence means stronger corroboration.

  • ClaimedHeadline60% confidence

    GitLab Patch Release: 16.7.3 16.6.5 16.5.7

  • ProbableSummary fact75% confidence

    On 12 January 2024, we released versions 16.7.3 16.6.5 16.5.7 for GitLab Community Edition and Enterprise Edition. These versions resolve a single issue with a database migration.