Monthly
Improper authorization in GitLab Enterprise Edition allows an authenticated reporter-level user who authored a merge request to reset that MR's approval rules, potentially bypassing mandatory code-review controls enforced by administrators. All GitLab EE versions from 13.1 through 19.3.0 are affected, with remediated releases published. A publicly available exploit exists via HackerOne, though the vulnerability is not listed in CISA KEV and the low CVSS score (3.5) reflects the constrained attack conditions requiring authentication and prior MR authorship.
Package protection rule bypass in GitLab CE/EE allows authenticated users holding developer-role permissions to circumvent registry protections that should restrict their write or publish actions. Affecting all GitLab Community and Enterprise Edition instances running versions 18.3 through 18.9.6, 18.10 through 18.10.5, and 18.11 through 18.11.2, an attacker with a legitimately provisioned developer account can undermine the integrity controls placed on protected packages. No public exploit code exists and no active exploitation has been identified at time of analysis; the EPSS score of 0.01% (1st percentile) and SSVC exploitation rating of 'none' confirm this is a low-urgency finding.
Improper authorization in GitLab Enterprise Edition allows an authenticated reporter-level user who authored a merge request to reset that MR's approval rules, potentially bypassing mandatory code-review controls enforced by administrators. All GitLab EE versions from 13.1 through 19.3.0 are affected, with remediated releases published. A publicly available exploit exists via HackerOne, though the vulnerability is not listed in CISA KEV and the low CVSS score (3.5) reflects the constrained attack conditions requiring authentication and prior MR authorship.
Package protection rule bypass in GitLab CE/EE allows authenticated users holding developer-role permissions to circumvent registry protections that should restrict their write or publish actions. Affecting all GitLab Community and Enterprise Edition instances running versions 18.3 through 18.9.6, 18.10 through 18.10.5, and 18.11 through 18.11.2, an attacker with a legitimately provisioned developer account can undermine the integrity controls placed on protected packages. No public exploit code exists and no active exploitation has been identified at time of analysis; the EPSS score of 0.01% (1st percentile) and SSVC exploitation rating of 'none' confirm this is a low-urgency finding.