CVE-2026-81839 Incorrect Authorization in GitLab

High 7.7 Published Updated

Authenticated users can execute arbitrary CI/CD pipelines in transferred projects with new group privileges due to improper policy record cleanup.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-81839?

CVE-2026-81839 is a high-severity missing authorization vulnerability in Gitlab Gitlab, published on 13 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

GitLab has remediated an issue in GitLab EE affecting all versions from 18.1 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 to execute arbitrary CI/CD pipelines in a transferred project with the new group's privileges due to improper cleanup of scheduled pipeline execution policy records.

Weakness: CWE-863

Which versions are affected by CVE-2026-81839?

1 open source package ship an affected version, including gitlab. It affects 1 product.

PackageAffectedFixed in
gitlab BitnamiFrom 18.1.019.2.8, 19.3.5, 19.4.2

Products include Gitlab Gitlab.

How do I fix CVE-2026-81839?

Upgrade gitlab to a fixed version for your release line: 19.2.8, 19.3.5 or 19.4.2.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-81839 being exploited?

There is no known exploitation of CVE-2026-81839 in the wild and no public exploit code.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2026-81839, GHSA-2qxc-8mjg-7g2x, MINI-49xg-5p4h-7vxj, MINI-8x4q-4qgc-9vw6, MINI-wgxr-m4mx-fffr, UBUNTU-CVE-2026-81839.

Is CVE-2026-81839 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free