Is CVE-2026-78335 exploited in the wild?

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

How severe is CVE-2026-78335?

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

Which products and versions are affected?

GitLab CE 19.1 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2; GitLab EE 19.1 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2.

Is there a fix for CVE-2026-78335?

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

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

Am I affected by CVE-2026-78335?

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-78335: GitLab incorrect authorization in fine-grained personal access tokens

CVE-2026-78335 · Severity: medium · CVSS 4.2 · Published 2026-10-13

GitLab, a widely-used DevOps platform for source code management and CI/CD, contains an authorization flaw affecting how it validates project-scoped personal access tokens. An authenticated user with a limited token scoped to specific projects could bypass access controls to modify integrations belonging to groups outside the token's permitted scope, potentially exposing group configurations or integrations to unauthorized modification.

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

Quick answers

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

An incorrect authorization check in GitLab CE/EE allows an authenticated user holding a project-scoped fine-grained Personal Access Token to modify group integrations outside the token's intended scope. The vulnerability results from insufficient authorization validation in the integration management logic. A network-based attack requires prior authentication and affects versions 19.1–19.4.1.

Affected products

GitLab GitLab CE 19.1 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2
GitLab GitLab EE 19.1 before 19.2.8, 19.3 before 19.3.5, 19.4 before 19.4.2

Timeline

2026-10-13: disclosed: Security advisory published
2026-10-12: patched: Versions 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.