CVE-2026-86341· NVD / CVE Program· CNA GitLab

Access Control Check Implemented After Asset is Accessed in GitLab

Noroxi assessment

Priority: Monitor (action score 17/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.36% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: GitLab GitLab 19.1.8, 19.2.6, 19.3.2.

Low priority for now. Upgrade to GitLab GitLab 19.1.8, 19.2.6, 19.3.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.4 · v3.1—No exploit Fix available

EUVD-2026-80249

Published: Sep 16, 2026
Updated: Sep 28, 2026
EPSS: 0.3% · 29th percentile
CWE: CWE-1280

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 17 / 40 · 4.4 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitLab: 4.4; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
gitlab	gitlab	cpe:2.3:a:gitlab:gitlab

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

gitlab gitlab17.1.0 and later · before 19.1.8
gitlab gitlab19.2.0 and later · before 19.2.6
gitlab gitlab19.3.0 and later · before 19.3.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitLab). Independent of NVD's CPE analysis and usually ahead of it.

GitLab GitLab
- 17.1 and later · before 19.1.8affected · semver
- 19.2 and later · before 19.2.6affected · semver
- 19.3 and later · before 19.3.2affected · semver

Same product

gitlab: all records

Other highest-scoring records for the same primary product.

CVE-2021-22205An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9.KEV
100Now
CVE-2026-85706Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLabKEV
98Now
CVE-2023-7028Weak Password Recovery Mechanism for Forgotten Password in GitLabKEV
97Now

Published before and after this one in the same product

← EarlierCVE-2026-8030Sep 16, 2026 · Missing Authorization in GitLab
17Monitor
← EarlierCVE-2025-14871Sep 16, 2026 · Allocation of Resources Without Limits or Throttling in GitLab
30Monitor
Later →CVE-2026-89078Sep 23, 2026 · Double Free in GitLab
39Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
GitLab GitLab	19.1.8	Vendor (CNA)
GitLab GitLab	19.2.6	Vendor (CNA)
GitLab GitLab	19.3.2	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

This vulnerability has been discovered internally by GitLab team member Peter Artsfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-3607125 days apartAccess Control Check Implemented After Asset is Accessed in GitLab
17Monitor
CVE-2026-748721 days apartAccess Control Check Implemented After Asset is Accessed in GitLab
14Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope