CVE-2023-3907Public exploitNetwork attack vector

Project Owner escalation via access token rotation

Published Dec 17, 2023 · Updated May 31, 2026

GitLab EE 16.0 through 16.4.3, 16.5 through 16.5.3, and 16.6 through 16.6.1 allows remote authenticated users to gain Owner access. The project access token rotation API permits a Maintainer to rotate an Owner-created token and returns the replacement token while preserving its Owner role. Exploitation requires Maintainer access to the same project and yields Owner capabilities for that project through the returned token.

CVSS severity4.9
Medium
EPSS probability0.68%
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

GitLab EE 16.0 through 16.4.3, 16.5 through 16.5.3, and 16.6 through 16.6.1 allows remote authenticated users to gain Owner access. The project access token rotation API permits a Maintainer to rotate an Owner-created token and returns the replacement token while preserving its Owner role. Exploitation requires Maintainer access to the same project and yields Owner capabilities for that project through the returned token.

The record

CVE
CVE-2023-3907
Published
Dec 17, 2023
Updated
May 31, 2026
Vendor
GitLab
Product
GitLab
Classifications
CWE-286, T1068
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Dec 17, 2023CVE publishedPublication date reported by the CVE source.
  2. May 31, 2026Record 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=16.0 <16.4.4
  2. Affected versionversion=16.5 <16.5.4
  3. Affected versionversion=16.6 <16.6.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=16.0 <16.4.4; version=16.5 <16.5.4; version=16.6 <16.6.2

Published CVSS scores

8.8NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.9GitLab Inc.CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N

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

CWE-286Incorrect User Management
T1068Exploitation for Privilege Escalation

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