Access Control Check Implemented After Asset is Accessed Affecting gitlab-rails-19.3 package, versions <19.3.2-r0


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.32% (25th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-GITLABRAILS193-20147312
  • published26 Sept 2026
  • disclosed16 Sept 2026

Introduced: 16 Sep 2026

NewCVE-2026-86341  (opens in a new tab)
CWE-1280  (opens in a new tab)

How to fix?

Upgrade Minimos:latest gitlab-rails-19.3 to version 19.3.2-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream gitlab-rails-19.3 package and not the gitlab-rails-19.3 package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

GitLab has remediated an issue in GitLab EE affecting all versions from 17.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an authenticated user with Owner or Maintainer permissions could have silently disabled protected environment deployment approval requirements, allowing unapproved deployments to reach production, due to improper access control checks performed after the protected resource was modified.