Is CVE-2026-8937 exploited in the wild?

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

How severe is CVE-2026-8937?

Medium severity, with a CVSS score of 4.3, published 29 September 2026.

Which products and versions are affected?

GitLab CE 19.0 to 19.2.6, 19.3.0 to 19.3.2, 19.4.0; GitLab EE 19.0 to 19.2.6, 19.3.0 to 19.3.2, 19.4.0.

Is there a fix for CVE-2026-8937?

A patch was published on 2026-09-23: Patches released in versions 19.2.7, 19.3.3, and 19.4.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-8937 attacked?

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

Am I affected by CVE-2026-8937?

Check whether you run GitLab CE 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-8937: GitLab missing authorization in Epic Issues REST API

CVE-2026-8937 · Severity: medium · CVSS 4.3 · Published 2026-09-29

GitLab CE/EE contains a missing authorization check in the Epic Issues REST API that allows authenticated users to read titles and descriptions of private child issues from projects they have no access to. An attacker with any GitLab account can view sensitive issue details linked to visible epics, potentially exposing confidential project information and business logic.

Technologies: GitLab CE, GitLab EE. Vendors: GitLab.

Quick answers

Is CVE-2026-8937 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-8937 being exploited in the wild.
How severe is CVE-2026-8937?: Medium severity, with a CVSS score of 4.3, published 29 September 2026.
Which products and versions are affected?: GitLab CE 19.0 to 19.2.6, 19.3.0 to 19.3.2, 19.4.0; GitLab EE 19.0 to 19.2.6, 19.3.0 to 19.3.2, 19.4.0.
Is there a fix for CVE-2026-8937?: A patch was published on 2026-09-23: Patches released in versions 19.2.7, 19.3.3, and 19.4.1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-8937 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-8937?: Check whether you run GitLab CE 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.

Technical details

An authenticated attacker can exploit missing authorization checks on linked work items within visible epics to bypass project-level access controls and read private child issue metadata. The vulnerability affects REST API calls enumerating or fetching child issues of accessible epics, with no scope validation against the requesting user's project permissions. A patch is available in versions 19.2.7, 19.3.3, and 19.4.1.

Affected products

GitLab GitLab CE 19.0 to 19.2.6, 19.3.0 to 19.3.2, 19.4.0
GitLab GitLab EE 19.0 to 19.2.6, 19.3.0 to 19.3.2, 19.4.0

Timeline

2026-09-23: patched: Patches released in versions 19.2.7, 19.3.3, and 19.4.1
2026-09-29: disclosed

References

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