Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-85529

Incorrect Authorization in GitLab

Overview

Published
13 Oct 2026
Modified
14 Oct 2026
Medium CVE
1 Registry packages
13 OS packages
3 Linux distributions
Yes Fix available

Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an unauthenticated user to read internal notes and confidential system notes on public projects due to improper authorization in the GraphQL API.

Source: OX vulnerability database

Severity

5.3 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Weakness: CWE-863

Affected packages · 1

Packages affected by CVE-2026-85529
EcosystemPackageVulnerableFixed in
Bitnami gitlab >=19.2.0, <19.2.8>=19.3.0, <19.3.5>=19.4.0, <19.4.2 19.2.819.3.519.4.2

Open a package to see all its vulnerabilities.

Operating systems · 6 fixes

chainguard 1 release · 2 packages

fixed 2
gitlab-runner-19-3 gitlab-runner-19-4
chainguard fixes for CVE-2026-85529
ReleasePackageFixed in
gitlab-runner-19-3 +1 19.3.5-r0
gitlab-runner-19-4 +1 19.4.2-r0

minimos 1 release · 3 packages

fixed 3
gitlab-cng-19-2 gitlab-cng-19-3 gitlab-cng-19-4
minimos fixes for CVE-2026-85529
ReleasePackageFixed in
gitlab-cng-19-2 +2 19.2.8-r0
gitlab-cng-19-3 +2 19.3.5-r0
gitlab-cng-19-4 +2 19.4.2-r0

wolfi 1 release · 1 package

fixed 1
gitlab-runner-19-3
wolfi fixes for CVE-2026-85529
ReleasePackageFixed in
gitlab-runner-19-3 19.3.5-r0

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.