Is CVE-2026-92528 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-92528 being exploited in the wild.

How severe is CVE-2026-92528?

Medium severity, with a CVSS score of 4.2, published 13 October 2026.

Which products and versions are affected?

GitLab EE 16.11 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2.

Is there a fix for CVE-2026-92528?

Yes: fixed in GitLab EE 19.2.8, 19.3.5, 19.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-92528 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-92528?

Check whether you run GitLab or GitLab EE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-92528: GitLab EE incorrect authorization in merge request approval eligibility

CVE-2026-92528 · Severity: medium · CVSS 4.2 · Published 2026-10-13

GitLab Enterprise Edition is a code repository and CI/CD platform used by development teams to manage source code and automate deployments. A flaw in merge request approval logic allowed authenticated users who had contributed code to a merge request to still approve it, bypassing a conflict-of-interest safeguard. An attacker with legitimate code contribution access could exploit this to merge unauthorized changes into protected branches.

Technologies: GitLab, GitLab EE. Vendors: GitLab.

Quick answers

Is CVE-2026-92528 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-92528 being exploited in the wild.
How severe is CVE-2026-92528?: Medium severity, with a CVSS score of 4.2, published 13 October 2026.
Which products and versions are affected?: GitLab EE 16.11 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2.
Is there a fix for CVE-2026-92528?: Yes: fixed in GitLab EE 19.2.8, 19.3.5, 19.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-92528 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-92528?: Check whether you run GitLab or GitLab EE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: GitLab EE 19.2.8, 19.3.5, 19.4.2

Technical details

An improper identity resolution vulnerability in GitLab EE's merge request approval eligibility check allows authenticated users to approve merge requests despite having contributed commits to them. The vulnerability affects the authorization logic that should prevent contributors from approving their own changes. An attacker with repository access and code contribution rights can bypass this restriction through crafted requests, potentially allowing unauthorized code merges.

Affected products

GitLab GitLab EE 16.11 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2

Timeline

2026-10-13: disclosed
2026-10-12: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.