Is CVE-2026-85529 exploited in the wild?

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

How severe is CVE-2026-85529?

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

Which products and versions are affected?

GitLab Community Edition 19.2 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2; GitLab Enterprise Edition 19.2 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2.

Is there a fix for CVE-2026-85529?

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-85529 attacked?

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

Am I affected by CVE-2026-85529?

Check whether you run GitLab Community Edition, GitLab Enterprise Edition or GitLab 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-85529: GitLab improper authorization in GraphQL notes API

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

GitLab Community and Enterprise Edition contain an authorization flaw in the GraphQL API that allows unauthenticated users to read internal and confidential system notes on public projects. This could expose sensitive project information, comments, or administrative notes that should not be visible. The vulnerability affects multiple current versions and requires patching immediately.

Technologies: GitLab Community Edition, GitLab Enterprise Edition, GitLab. Vendors: GitLab.

Quick answers

Is CVE-2026-85529 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-85529 being exploited in the wild.
How severe is CVE-2026-85529?: Medium severity, with a CVSS score of 5.3, published 13 October 2026.
Which products and versions are affected?: GitLab Community Edition 19.2 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2; GitLab Enterprise Edition 19.2 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2.
Is there a fix for CVE-2026-85529?: 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-85529 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-85529?: Check whether you run GitLab Community Edition, GitLab Enterprise Edition or GitLab 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

An improper authorization check in the GraphQL notes widget allows unauthenticated attackers to bypass access controls and retrieve internal notes and confidential system notes from public projects. The flaw exists in GraphQL API endpoint handling where authorization is not properly enforced. Patches are available in GitLab CE/EE 19.2.8, 19.3.5, and 19.4.2.

Affected products

GitLab Community Edition 19.2 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2
GitLab Enterprise Edition 19.2 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.