CVE-2023-3509Public exploitNetwork attack vector

Authenticated deploy-key title modification via missing access check

Published Feb 21, 2024 · Updated Aug 14, 2026

Incorrect authorization in GitLab before 16.7.6, 16.8 through 16.8.2, and 16.9.0 allows remote authenticated users to alter shared deploy-key titles. The privately accessible deploy-keys listing omits an access check, letting a member expose keys from another project through an attacker-controlled project and submit title edits. A group role below Maintainer is required; the change can mislead maintainers about key purpose, while exposure is limited to deploy-key metadata rather than private key material.

CVSS severity3.7
Low
EPSS probability0.32%
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

Incorrect authorization in GitLab before 16.7.6, 16.8 through 16.8.2, and 16.9.0 allows remote authenticated users to alter shared deploy-key titles. The privately accessible deploy-keys listing omits an access check, letting a member expose keys from another project through an attacker-controlled project and submit title edits. A group role below Maintainer is required; the change can mislead maintainers about key purpose, while exposure is limited to deploy-key metadata rather than private key material.

The record

CVE
CVE-2023-3509
Published
Feb 21, 2024
Updated
Aug 14, 2026
Vendor
GitLab
Product
GitLab
Classifications
CWE-863, T1565
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Feb 21, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 14, 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=0 <16.7.6
  2. Affected versionversion=16.8 <16.8.3
  3. Affected versionversion=16.9 <16.9.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=0 <16.7.6; version=16.8 <16.8.3; version=16.9 <16.9.1

Published CVSS scores

3.7GitLab Inc.CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N
5.4NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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-863Incorrect Authorization
T1565Data 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