Skip to content
VulniPulse
Medium5.5GitLab Updated

Medium [CVE-2026-3035] Authentication Bypass Using an Alternate Path or Channel in GitLab

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

CVE-2026-3035 Published Aug 26, 2026Updated by vendor Aug 26, 2026
Affected products & platforms
GitLabUnclassified
Open vendor 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 32 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 11.3 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with project Maintainer permissions could have accessed the terminal of a protected environment they were not authorized to use due to improper authorization checks.

Affected versions
  • GitLab 11.3 before 19.1.7
  • GitLab 19.2 before 19.2.5
  • GitLab 19.3 before 19.3.1

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

Fixed versions
  • 19.1.7
  • 19.2.5
  • 19.3.1

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

Mitigation

Upgrade to a fixed release: 19.1.7, 19.2.5, 19.3.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 2 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.