CVE-2022-1680Public exploitNetwork attack vector

Group-owner account takeover via SCIM email change

Published Jun 6, 2022 · Updated Aug 3, 2024

Improper authorization in GitLab EE 11.10 through 14.9.4, 14.10.0 through 14.10.3, and 15.0.0 allows remote authenticated users to take over accounts. The group SCIM API associates an invited username and email with an existing account, then accepts a PATCH that replaces that account’s email with an attacker-controlled address. A Premium group owner needs Group SAML SSO and SCIM enabled, and takeover succeeds only when the targeted account lacks two-factor authentication; display names and usernames can also be changed.

CVSS severity9.9
Critical
EPSS probability15.90%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper authorization in GitLab EE 11.10 through 14.9.4, 14.10.0 through 14.10.3, and 15.0.0 allows remote authenticated users to take over accounts. The group SCIM API associates an invited username and email with an existing account, then accepts a PATCH that replaces that account’s email with an attacker-controlled address. A Premium group owner needs Group SAML SSO and SCIM enabled, and takeover succeeds only when the targeted account lacks two-factor authentication; display names and usernames can also be changed.

The record

CVE
CVE-2022-1680
Published
Jun 6, 2022
Updated
Aug 3, 2024
Vendor
GitLab
Product
GitLab
Classifications
T1098
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 6, 2022CVE publishedPublication date reported by the CVE source.
  2. Aug 3, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>=11.0, <14.9.5
  2. Affected versionversion=>=14.10.0, <14.10.4
  3. Affected versionversion=>=15.0.0, <15.0.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=>=11.0, <14.9.5; version=>=14.10.0, <14.10.4; version=>=15.0.0, <15.0.1

Published CVSS scores

8.8UbuntuCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
9.9GitLabCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

T1098Account Manipulation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo