Is CVE-2026-16275 exploited in the wild?

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

How severe is CVE-2026-16275?

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

Which products and versions are affected?

GitLab CE 17.4 through 19.2.7, 19.3.0 through 19.3.4, 19.4.0 through 19.4.1; GitLab EE 17.4 through 19.2.7, 19.3.0 through 19.3.4, 19.4.0 through 19.4.1.

Is there a fix for CVE-2026-16275?

Yes: fixed in GitLab CE/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-16275 attacked?

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

Am I affected by CVE-2026-16275?

Check whether you run GitLab, 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-16275: GitLab CE/EE incorrect authorization in notes

CVE-2026-16275 · Severity: medium · CVSS 5.3 · Published 2026-10-13

GitLab is a DevOps platform used by organizations to manage code repositories and CI/CD pipelines. An authorization flaw allows unauthenticated users to read confidential notes attached to public projects, potentially exposing sensitive comments and discussions that should only be visible to project members. An attacker can access this information without logging in or having any permissions.

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

Quick answers

Is CVE-2026-16275 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-16275 being exploited in the wild.
How severe is CVE-2026-16275?: Medium severity, with a CVSS score of 5.3, published 13 October 2026.
Which products and versions are affected?: GitLab CE 17.4 through 19.2.7, 19.3.0 through 19.3.4, 19.4.0 through 19.4.1; GitLab EE 17.4 through 19.2.7, 19.3.0 through 19.3.4, 19.4.0 through 19.4.1.
Is there a fix for CVE-2026-16275?: Yes: fixed in GitLab CE/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-16275 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-16275?: Check whether you run GitLab, 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.

How to fix

Fixed in: GitLab CE/EE 19.2.8, 19.3.5, 19.4.2

Technical details

The vulnerability is an incorrect authorization check in the notes feature that fails to enforce access controls for confidential notes on public projects. An unauthenticated network attacker can bypass authorization and read notes that should be restricted. The issue affects the GraphQL notes widget and related API endpoints, and has been fixed in the patched versions.

Affected products

GitLab GitLab CE 17.4 through 19.2.7, 19.3.0 through 19.3.4, 19.4.0 through 19.4.1
GitLab GitLab EE 17.4 through 19.2.7, 19.3.0 through 19.3.4, 19.4.0 through 19.4.1

Timeline

2026-10-13: disclosed
2026-10-12: patched: Patch releases 19.4.2, 19.3.5, 19.2.8 released

References

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