CVE-2026-7487

lowpriority · track · 0EPSS 0.003 · 24 %ileDEUS

grimoire priorityP3 · Track

Exploitable?

—

no known exploitation

Likely / severe?

0.32% (24th) EPSS

CVSS 3.5 · low

Is it mine?

12 products

Check your exposure

Who says so?

3 sources

cert_bund · nvd · osv

EPSS · scored 2026-10-27

GitLab has remediated an issue in GitLab EE affecting all versions from 13.1 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with reporter-role permissions who authored a merge request could have reset merge request approval rules due to improper authorization checks.

cvss

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

3.5

010

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

v3.13.5lowCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:Nsecondary · cve@gitlab.comexploitability 2.1 · impact 1.4

v3.13.2lowCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/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 (12)

Products and version ranges known to be affected.

Open Source GitLab <19.1.7all versionscert_bundDE
Open Source GitLab <19.2.5all versionscert_bundDE
Open Source GitLab <19.3.1all versionscert_bundDE
Open Source GitLab< 19.1.7cert_bundDE
Open Source GitLab< 19.2.5cert_bundDE
Open Source GitLab< 19.3.1cert_bundDE
gitlab gitlab13.1.0 → 19.1.7nvdUScpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
gitlab gitlab19.2.0 → 19.2.5nvdUScpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
gitlab gitlab= 19.3.0nvdUScpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*
Bitnami gitlab13.1.0 → 19.1.7osvUSpkg:bitnami/gitlab
Bitnami gitlab19.2.0 → 19.2.5osvUSpkg:bitnami/gitlab
Bitnami gitlab19.3.0 → 19.3.1osvUSpkg:bitnami/gitlab

advisories (2)

Vendor and ecosystem advisories describing this.

WID-SEC-W-2026-3029GitLab: Mehrere SchwachstellenDeutsch2026-08-25csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in GitLab ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Daten zu manipulieren und um Sicherheitsvorkehrungen zu umgehen.
BIT-gitlab-2026-7487Access Control Check Implemented After Asset is Accessed in GitLab2026-09-01vendor · osvUS
GitLab has remediated an issue in GitLab EE affecting all versions from 13.1 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user with reporter-role permissions who authored a merge request could have reset merge request approval rules due to improper authorization checks.

sources

Which sources assert this record, and when.

cert_bund nvd osv NVD CVE.org MITRE

published 2026-08-26modified 2026-08-31

references (3) nvd

External citations — patches, advisories, analysis.

https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-1-released/Release NotesVendor Advisory
https://gitlab.com/gitlab-org/gitlab/-/work_items/598657Issue TrackingPermissions Required
https://hackerone.com/reports/3669140Permissions RequiredThird Party Advisory

scry

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

Free scan