Skip to content
VulniPulse
Advisory severityMedium5.9GitLab Updated

Medium [CVE-2026-16255] GitLab has remediated an issue in GitLab EE affecting all versions from 12.0 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when the instance-wide SAML or LDAP membership lock was enabled, an authenticated user could have granted or accepted project and group membership outside the identity provider's control, due to incomplete enforcement of the membership lock on requests created before the lock was enabled

This medium-severity GitLab advisory covers CVE-2026-16255 affecting GitLab.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-16255 Source published Source updated

VulniPulse record published Record updated

CVE-2026-16255
Affected products & platforms
GitLabUnclassified
Open source advisory

Android app · Google Play

Monitor future GitLab CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

GitLab has remediated an issue in GitLab EE affecting all versions from 12.0 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when the instance-wide SAML or LDAP membership lock was enabled, an authenticated user could have granted or accepted project and group membership outside the identity provider's control, due to incomplete enforcement of the membership lock on requests created before the lock was enabled.

Affected versions
  • before 19.3.6
  • before 19.4.3
  • before 19.5.1

Official advisory · high-confidence parse· fetched 7 hours ago·verify at source

Fixed versions
  • 19.3.6
  • 19.4.3
  • 19.5.1

Official advisory · high-confidence parse· fetched 7 hours ago·verify at source

Mitigation

Upgrade to a fixed release: 19.3.6, 19.4.3, 19.5.1. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 7 hours ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.