CVE-2026-2900 | Missing Authorization in GitLab

GitLab has remediated an issue in GitLab EE affecting all versions from 16.10 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that when instance-level approval rule editing prevention was enabled, could have allowed an authenticated user with Maintainer permissions to modify or delete project approval rules due to missing authorization checks.

Published: 2026-05-14 Last update: 2026-05-16 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-2900 is rated Low Risk (15.3/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.22%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-2900

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.22% +0.21%
2 2026-05-14 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-2900

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
2.7 3.1 LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 1.2 1.4 [email protected]

Weakness enumeration for CVE-2026-2900

GitHub Security Advisory for CVE-2026-2900

GHSA-8xwh-m77v-v26p · Severity: low — GitLab has remediated an issue in GitLab EE affecting all versions from 16.10 before 18.9.7, 18...

OS Trackers for CVE-2026-2900

vendor priority summary link
debian unimportant CVE-2026-2900 unimportant priority: Debian including 1 source packages (gitlab), 1 status rows across 1 suites (sid): resolved 1. https://security-tracker.debian.org/tracker/CVE-2026-2900
ubuntu medium CVE-2026-2900 medium priority: Ubuntu including 1 source packages (gitlab), 5 status rows across 5 suites (jammy, noble, questing, resolute, upstream): DNE 4, not-affected 1. https://ubuntu.com/security/CVE-2026-2900

Affected software / configurations for CVE-2026-2900

Vendor Product Version Raw CPE
gitlab gitlab >= 16.10.0, < 18.9.7 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
gitlab gitlab >= 18.10.0, < 18.10.6 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
gitlab gitlab >= 18.11.0, < 18.11.3 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*

References for CVE-2026-2900

cvelogic Threat Intelligence