rootpwn

Advisories

GitLab Security Release 16.3.1/16.2.5/16.1.5: Fixes for Privilege Escalation and Token Leakage

GitLab has issued security patches for versions 16.3.1, 16.2.5, and 16.1.5 to fix a privilege escalation flaw that allowed external users to gain internal group access and a token leakage issue that could expose Sentry credentials. All installations of CE and EE should upgrade immediately. GitLab.com is already running the patched version.

What happened

GitLab released security patches for versions 16.3.1, 16.2.5, and 16.1.5 to address two critical issues affecting both Community and Enterprise Editions.

Impact

  • Privilege escalation: an external user could gain internal group access via a group service account (medium severity).
  • Token leakage: a maintainer could expose a Sentry token by modifying configuration, potentially exposing sensitive data.

What to do

All installations running any of the affected versions must upgrade immediately to the patched releases. GitLab.com is already running the updated version. Verify your deployment type (omnibus, source, helm) and apply the corresponding update.

Best practices

Maintain a regular patch cadence, monitor GitLab’s security release schedule, and restrict external user permissions to the minimum required.

GitLab Security Patch Privilege Escalation Token Leakage GitLab CE GitLab EE Vulnerability

← All news