CVE-2026-82632: GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.9 before 19.2.8, 19.3 before 19.3.5, and…

CVE-2026-82632 · Severity: low · CVSS 3.1 · Published 2026-10-13

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.9 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 authenticated user with a fine-grained Personal Access Token scoped only to user-boundary import permissions to import projects into group namespaces beyond the token's intended scope, due to incorrect authorization of the import target namespace.

Technologies: GitLab. Vendors: GitLab.

Quick answers

Is CVE-2026-82632 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-82632 being exploited in the wild.
How severe is CVE-2026-82632?
Low severity, with a CVSS score of 3.1, published 13 October 2026.
Which products and versions are affected?
GitLab. The advisory does not name versions.
Is there a fix for CVE-2026-82632?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2026-82632?
Check whether you run GitLab. 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.

Affected products

  • GitLab

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