Is CVE-2026-6336 exploited in the wild?

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

How severe is CVE-2026-6336?

Medium severity, with a CVSS score of 5.3, published 29 July 2026.

Which products and versions are affected?

GitLab 16.6 to 19.0.5, 19.1 to 19.1.3, 19.2 to 19.2.1.

Is there a fix for CVE-2026-6336?

A patch was published on 2026-07-29: GitLab released versions 19.2.1, 19.1.3, and 19.0.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-6336 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-6336?

Check whether you run 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-6336: GitLab CE/EE incorrect authorization in project import status

CVE-2026-6336 · Severity: medium · CVSS 5.3 · Published 2026-07-29

GitLab, a platform for software development and version control, has addressed a security flaw that could allow unauthorized individuals to view sensitive information about project imports. An attacker could potentially see details regarding where a project was imported from, which may include internal source information. This issue affects self-managed GitLab Community and Enterprise editions, and users are advised to upgrade to the latest patched versions to protect their data.

Technologies: GitLab. Vendors: GitLab.

Quick answers

Is CVE-2026-6336 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-6336 being exploited in the wild.
How severe is CVE-2026-6336?: Medium severity, with a CVSS score of 5.3, published 29 July 2026.
Which products and versions are affected?: GitLab 16.6 to 19.0.5, 19.1 to 19.1.3, 19.2 to 19.2.1.
Is there a fix for CVE-2026-6336?: A patch was published on 2026-07-29: GitLab released versions 19.2.1, 19.1.3, and 19.0.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-6336 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-6336?: Check whether you run 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.

Technical details

An incorrect authorization vulnerability (CWE-863) exists in GitLab CE/EE within the project import status functionality. The flaw is caused by a missing authorization check that allows an unauthenticated, remote attacker to view project import source information. This could lead to the disclosure of metadata or source details related to how projects were migrated into the instance. The issue affects versions 16.6 through 19.0.5, 19.1 through 19.1.3, and 19.2 through 19.2.1. GitLab has released patches in versions 19.0.5, 19.1.3, and 19.2.1 to address this vulnerability.

Affected products

GitLab GitLab CE/EE 16.6 to 19.0.5, 19.1 to 19.1.3, 19.2 to 19.2.1

Timeline

2026-07-29: patched: GitLab released versions 19.2.1, 19.1.3, and 19.0.5.
2026-07-29: advisory: NVD published the CVE record.

References

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