GitLab up to 19.1.7/19.2.5/19.3.1 Compliance Framework Management improper authorization

Summaryinfo

A vulnerability was found in GitLab up to 19.1.7/19.2.5/19.3.1. It has been rated as problematic. Affected is an unknown function of the component Compliance Framework Management. The manipulation leads to improper authorization. This vulnerability is listed as CVE-2026-16794. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in GitLab up to 19.1.7/19.2.5/19.3.1. It has been rated as problematic. This issue affects an unknown function of the component Compliance Framework Management. The manipulation with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Impacted is integrity. The summary by CVE is:

GitLab has remediated an issue in GitLab EE affecting all versions from 18.11 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could have allowed an authenticated user with the Security Manager role to execute arbitrary CI/CD jobs and access protected variables within group projects due to improper authorization controls on compliance framework management.

It is possible to read the advisory at gitlab.com. The identification of this vulnerability is CVE-2026-16794 since 07/23/2026. The exploitation is known to be easy. The attack may be initiated remotely. Additional levels of successful authentication are necessary for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1548.002 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 346273 (GitLab 18.11 < 19.1.8 / 19.2 < 19.2.6 / 19.3 < 19.3.2 (CVE-2026-16794)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 19.1.8, 19.2.6 or 19.3.2 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (346273) and CERT Bund (WID-SEC-2026-3315). Be aware that VulDB is the high quality source for vulnerability data.

Affected

• Open Source GitLab

Productinfo

Type

• Bug Tracking Software

Name

• GitLab

Version

• 19.1.0
• 19.1.1
• 19.1.2
• 19.1.3
• 19.1.4
• 19.1.5
• 19.1.6
• 19.1.7
• 19.2.0
• 19.2.1
• 19.2.2
• 19.2.3
• 19.2.4
• 19.2.5
• 19.3.0
• 19.3.1

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion