Skip to content
VulniPulse
Advisory severityMedium4.8GitLab

Medium [CVE-2023-5226] Improper Control of Generation of Code ('Code Injection') in GitLab

This medium-severity GitLab advisory covers CVE-2023-5226 affecting GitLab.

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

CVE-2023-5226 Source published Source updated

VulniPulse record published

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

An issue has been discovered in GitLab affecting all versions before 16.4.3, all versions starting from 16.5 before 16.5.3, all versions starting from 16.6 before 16.6.1. Under certain circumstances, a malicious actor bypass prohibited branch checks using a specially crafted branch name to manipulate repository content in the UI.

Affected versions
  • GitLab before 16.4.3
  • GitLab 16.5 before 16.5.3
  • GitLab 16.6 before 16.6.1

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

Fixed versions
  • 16.4.3
  • 16.5.3
  • 16.6.1

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

Mitigation

Upgrade to a fixed release: 16.4.3, 16.5.3, 16.6.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 months 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.