CVE-2026-7487: gitlab — Fix

Description

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.

Is your site exposed to CVE-2026-7487?

Run a free security scan — no signup, results in seconds.

CVSS v3.1 Score

3.5

LOW

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N

EPSS — Exploit Prediction

0.0023

Probability of exploitation

0.13%

Percentile rank

EPSS estimates the probability that this vulnerability will be exploited in the wild within the next 30 days. A higher score means more likely to be exploited.

Weakness Type (CWE)

CWE-1280 CWE-1280

Affected Products

Vendor	Product	Versions
gitlab	gitlab	13.1.0 — 19.1.7
gitlab	gitlab	19.2.0 — 19.2.5
gitlab	gitlab	All

References

Advisories & Patches

https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-1-released/

Other References

https://gitlab.com/gitlab-org/gitlab/-/work_items/598657 https://hackerone.com/reports/3669140

Frequently Asked Questions

What is CVE-2026-7487? +

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. It has a CVSS v3.1 base score of 3.5 (LOW).

How severe is CVE-2026-7487? +

CVE-2026-7487 has a CVSS v3.1 score of 3.5 out of 10, rated LOW. This is a low-severity vulnerability with limited impact. The EPSS score is 0.0023, placing it in the 0th percentile for exploitation probability.

What products are affected by CVE-2026-7487? +

CVE-2026-7487 affects products from gitlab, specifically: gitlab. Check the affected products table above for specific version ranges.

How do I check if I'm vulnerable to CVE-2026-7487? +

You can use Secably's free Website Scanner to check your website for known vulnerabilities. For infrastructure scanning, use the Port Scanner to identify exposed services that may be affected. Check the vendor advisories linked above for specific patch and version information.

Related Vulnerabilities

CVE-2026-86341 4.4

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 …

CVE-2026-3607 4.3

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.3 before 18.9.7, 18.10 before 18.10.6, and 18.11 …

CVE-2023-7028 10.0

An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9, …

CVE-2024-45409 10.0

The Ruby SAML library is for implementing the client side of a SAML authorization. Ruby-SAML in <= 12.2 and 1.13.0 …

CVE-2026-85706 10.0

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 …

CVE-2024-0402 9.9

An issue has been discovered in GitLab CE/EE affecting all versions from 16.0 prior to 16.6.6, 16.7 prior to 16.7.4, …

CVE-2026-7487