CVE-2026-86341

mediumpriority · track · 0EPSS 0.004 · 29 %ileDEUS

grimoire priorityP3 · Track

Exploitable?

—

no known exploitation

Likely / severe?

0.36% (29th) EPSS

CVSS 4.4 · medium

Is it mine?

13 products

Check your exposure

Who says so?

3 sources

cert_bund · nvd · osv

EPSS · scored 2026-10-22

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.

cvss

Technical severity, 0–10. One row per scoring source.

4.4

010

base score 0–10 · higher = more severe · hover a vector to decode

v3.14.4mediumCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:Nsecondary · cve@gitlab.comexploitability 0.7 · impact 3.6

v3.14.1mediumCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N/E:Usecondary · CVSS-BT (t0sche)

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-1280US

affected products (13)

Products and version ranges known to be affected.

Open Source GitLab <18.11.12all versionscert_bundDE
Open Source GitLab <19.0.9all versionscert_bundDE
Open Source GitLab< 18.11.12cert_bundDE
Open Source GitLab< 19.0.9cert_bundDE
Open Source GitLab< 19.1.8cert_bundDE
Open Source GitLab< 19.2.6cert_bundDE
Open Source GitLab< 19.3.2cert_bundDE
gitlab gitlab17.1.0 → 19.1.8nvdUScpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
gitlab gitlab19.2.0 → 19.2.6nvdUScpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
gitlab gitlab19.3.0 → 19.3.2nvdUScpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
Bitnami gitlab17.1.0 → 19.1.8osvUSpkg:bitnami/gitlab
Bitnami gitlab19.2.0 → 19.2.6osvUSpkg:bitnami/gitlab
Bitnami gitlab19.3.0 → 19.3.2osvUSpkg:bitnami/gitlab

advisories (2)

Vendor and ecosystem advisories describing this.

WID-SEC-W-2026-3315GitLab: Mehrere SchwachstellenDeutsch2026-09-10csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in GitLab ausnutzen, um beliebigen Code auszuführen, erweiterte Berechtigungen zu erlangen, Sicherheitsmaßnahmen zu umgehen, sensible Informationen oder Anmeldedaten offenzulegen, Daten zu manipulieren, Cross-Site-Scripting-Angriffe durchzuführen oder Denial-of-Service-Zustände zu verursachen.
BIT-gitlab-2026-86341Access Control Check Implemented After Asset is Accessed in GitLab2026-09-25vendor · osvUS
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.

sources

Which sources assert this record, and when.

cert_bund nvd osv NVD CVE.org MITRE

published 2026-09-16modified 2026-09-28

references (2) nvd

External citations — patches, advisories, analysis.

https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-2-released/Release NotesVendor Advisory
https://gitlab.com/gitlab-org/gitlab/-/work_items/600088Broken Link

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan