CVE-2023-2030Public exploitNetwork attack vector

Signed-commit metadata forgery via misparsed GPG signature

Published Jan 12, 2024 · Updated Nov 20, 2025

Improper signature verification in affected GitLab versions allows remote authenticated users to alter signed-commit metadata. Gitaly's extractSignatures function treats every header after gpgsig as signature data, while GPGME ignores the trailing bytes and verifies data that omits those headers. Repository write access and a forged commit are required; altered author, date, or parent headers can still appear Verified to reviewers.

CVSS severity3.5
Low
EPSS probability0.39%
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 signature verification in affected GitLab versions allows remote authenticated users to alter signed-commit metadata. Gitaly's extractSignatures function treats every header after gpgsig as signature data, while GPGME ignores the trailing bytes and verifies data that omits those headers. Repository write access and a forged commit are required; altered author, date, or parent headers can still appear Verified to reviewers.

The record

CVE
CVE-2023-2030
Published
Jan 12, 2024
Updated
Nov 20, 2025
Vendor
GitLab
Product
GitLab
Classifications
CWE-347, T1565.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jan 12, 2024CVE publishedPublication date reported by the CVE source.
  2. Nov 20, 2025Record 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=12.2 <16.5.6
  2. Affected versionversion=16.6 <16.6.4
  3. Affected versionversion=16.7 <16.7.2

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=12.2 <16.5.6; version=16.6 <16.6.4; version=16.7 <16.7.2

Published CVSS scores

3.5GitLab Inc.CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
5.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-347Improper Verification of Cryptographic Signature
T1565.001Stored Data 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