CVE-2022-2227

What it is

Improper access control in the runner jobs API in GitLab CE/EE affecting all versions prior to 14.10.5, 15.0 prior to 15.0.4, and 15.1 prior to 15.1.1 allows a previous maintainer of a project with a specific runner to access job and project meta data under certain conditions

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. Limited direct impact.

Exploit odds

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

Fix

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

Timeline

1. 2022-07-01 16:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 04:41 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.8% in the next 30 days (EPSS).
• Severity: 3.1 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2022-07-01 16:15 UTC

Last modified

2026-06-17 04:41 UTC

Exploit probability

0.8% · EPSS, next 30 days

Weakness

CWE-732 · Incorrect permission assignment

Record status

Modified

Affected

• GitLab < 14.10.5
• GitLab < 15.0.4
• GitLab 15.1.0

Attack profile CVSS 3.1 · 3.1

Attack vector

Network

Complexity

High

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

None

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-2227.md and follow it. Check whether this project is affected by CVE-2022-2227. 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