Is CVE-2026-81839 exploited in the wild?

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

How severe is CVE-2026-81839?

High severity, with a CVSS score of 7.7, published 13 October 2026.

Which products and versions are affected?

GitLab EE 18.1 through 19.2.7, 19.3 through 19.3.4, 19.4 through 19.4.1.

Is there a fix for CVE-2026-81839?

Yes: fixed in GitLab 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-81839 attacked?

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

Am I affected by CVE-2026-81839?

Check whether you run GitLab 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-81839: GitLab EE incorrect authorization in scheduled pipeline execution policy

CVE-2026-81839 · Severity: high · CVSS 7.7 · Published 2026-10-13

GitLab Enterprise Edition, a DevOps platform used to manage code repositories and automate software delivery, has a flaw in how it handles CI/CD pipeline policies during project transfers. An authenticated user could execute arbitrary CI/CD pipelines in a transferred project using the new group's elevated privileges due to improper cleanup of scheduling rules. This could allow an attacker to run unauthorized code deployments or access sensitive project data.

Technologies: GitLab, GitLab EE. Vendors: GitLab.

Quick answers

Is CVE-2026-81839 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-81839 being exploited in the wild.
How severe is CVE-2026-81839?: High severity, with a CVSS score of 7.7, published 13 October 2026.
Which products and versions are affected?: GitLab EE 18.1 through 19.2.7, 19.3 through 19.3.4, 19.4 through 19.4.1.
Is there a fix for CVE-2026-81839?: Yes: fixed in GitLab 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-81839 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-81839?: Check whether you run GitLab 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 EE 19.2.8, 19.3.5, 19.4.2

Technical details

An authenticated user can exploit improper cleanup of scheduled pipeline execution policy records during project transfer to execute arbitrary CI/CD pipelines with the new group's privileges, resulting in privilege escalation. The vulnerability affects GitLab EE versions 18.1 through 19.4.1, requiring network access and prior authentication to exploit. A fix is available in versions 19.2.8, 19.3.5, and 19.4.2.

Affected products

GitLab GitLab EE 18.1 through 19.2.7, 19.3 through 19.3.4, 19.4 through 19.4.1

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.