CVE-2023-4317 Incorrect Authorization in GitLab

Medium 4.3 Published 1 Dec 2023 Updated 20 Nov 2025

A Developer role user can improperly update pipeline schedules from unprotected to protected branches, bypassing intended branch protection controls.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2023-4317?

CVE-2023-4317 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 1 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

An issue has been discovered in GitLab affecting all versions starting from 9.2 before 16.4.3, all versions starting from 16.5 before 16.5.3, all versions starting from 16.6 before 16.6.1. It was possible for a user with the Developer role to update a pipeline schedule from an unprotected branch to a protected branch.

Weakness: CWE-863

Which versions are affected by CVE-2023-4317?

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

Package	Affected	Fixed in
`gitlab` Bitnami	From `9.2.0`	`16.4.3, 16.5.3, 16.6.1`

Products include Gitlab Gitlab.

How do I fix CVE-2023-4317?

Upgrade gitlab to a fixed version for your release line: 16.4.3, 16.5.3 or 16.6.1.

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

Is CVE-2023-4317 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2023-4317, GHSA-33j6-gqw4-wvvg.