CVE-2022-4331

What it is

An issue has been discovered in GitLab EE affecting all versions starting from 15.1 before 15.7.8, all versions starting from 15.8 before 15.8.4, all versions starting from 15.9 before 15.9.2. If a group with SAML SSO enabled is transferred to a new namespace as a child group, it's possible previously removed malicious maintainer or owner of the child group can still gain access to the group via SSO or a SCIM token to perform actions on the group.

At a glance

Exploitability

Can be exploited over the network with an admin-level account, but needs a user to act. High risk of data exposure, data tampering.

Exploit odds

0.7% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2023-03-09 22:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 05:20 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.7% in the next 30 days (EPSS).
• Severity: 5.7 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2023-03-09 22:15 UTC

Last modified

2026-06-17 05:20 UTC

Exploit probability

0.7% · EPSS, next 30 days

Weakness

CWE-284 · Improper access control

Record status

Modified

Affected

• GitLab < 15.7.8
• GitLab < 15.8.4
• GitLab < 15.9.2

Attack profile CVSS 3.1 · 5.7

Attack vector

Network

Complexity

High

Privileges needed

High

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2022-4331.md and follow it. Check whether this project is affected by CVE-2022-4331. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge