Which products and versions are affected by CVE-2022-1162?

Affected: GitLab versions >= 14.7.0, >= >=14.9, <14.9.2. The full list is in the CVE brief.

Is CVE-2022-1162 being exploited in the wild?

It is not listed in any known-exploited vulnerabilities catalog.

Is CVE-2022-1162 in the CISA KEV catalog?

No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

Is there a public exploit for CVE-2022-1162?

Public exploit code is available.

Is there a fix for CVE-2022-1162?

Fixed versions are available, including GitLab 14.7.7, GitLab 14.8.5, GitLab 14.9.2.

How urgently should CVE-2022-1162 be patched?

Brandefense priority: patch immediately, because it is very likely to be exploited soon.

Request A Demo

Vulnerability Intelligence

CVE-2022-1162

Q: What is CVE-2022-1162?

A hardcoded password was set for accounts registered using an OmniAuth provider (e.g.

Q: Is CVE-2022-1162 being exploited in the wild?

It is not listed in any known-exploited vulnerabilities catalog.

Q: Is CVE-2022-1162 in the CISA KEV catalog?

No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.

Q: Is there a public exploit for CVE-2022-1162?

Public exploit code is available.

Q: Is there a fix for CVE-2022-1162?

Fixed versions are available, including GitLab 14.7.7, GitLab 14.8.5, GitLab 14.9.2.

Q: How urgently should CVE-2022-1162 be patched?

Brandefense priority: patch immediately, because it is very likely to be exploited soon.

CriticalPublic exploit

A hardcoded password was set for accounts registered using an OmniAuth provider (e.g.

Published May 5, 2022 · Updated Sep 11, 2026 · Also known as BIT-gitlab-2022-1162, TR-22-0328, UBUNTU-CVE-2022-1162

Key Facts

Patch immediately

CVE-2022-1162 is a critical-severity vulnerability (CVSS 9.8 v3.1) affecting GitLab.
It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
EPSS estimates a 76% probability of exploitation in the next 30 days.
Fixed versions are available, including GitLab 14.7.7, GitLab 14.8.5, GitLab 14.9.2.
Brandefense priority: patch immediately, because it is very likely to be exploited soon.

CVSS v3.1

9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS (30-day exploit likelihood)

76%

Higher than 99.5% of all scored CVEs

Exploited in the wild

No known

Not in a known-exploited catalog

Public exploit code

Available

Proof-of-concept or weaponized module

Get the full CVE-2022-1162 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

Description

A hardcoded password was set for accounts registered using an OmniAuth provider (e.g. OAuth, LDAP, SAML) in GitLab CE/EE versions 14.7 prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2 allowing attackers to potentially take over accounts

Affected Products

6 affected entries in total

Product	Affected versions	Fixed in
GitLabGitlab	>= 14.7.0, >= >=14.9, <14.9.2	14.7.7

Patched Releases

GitLab

14.7.7, 14.8.5, 14.9.2, 15.10.8+ds1-2

Timeline

Publicly disclosed
May 5, 2022
Last updated
Sep 11, 2026

Weakness Type

CWE-798 Use of Hard-coded Credentials

References

7 more references in the full CVE brief

FAQ

Common Questions.

A hardcoded password was set for accounts registered using an OmniAuth provider (e.g.
Affected: GitLab versions >= 14.7.0, >= >=14.9, <14.9.2. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
Public exploit code is available.
Fixed versions are available, including GitLab 14.7.7, GitLab 14.8.5, GitLab 14.9.2.
Brandefense priority: patch immediately, because it is very likely to be exploited soon.

Is CVE-2022-1162 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.

Request A Demo