How severe is CVE-2019-19629?

CVE-2019-19629 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2019-19629 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (63rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-19629?

CVE-2019-19629 affects Gitlab. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2019-19629?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2019-19629 published?

CVE-2019-19629 was published on 2020-01-05 and last updated on 2026-06-17.

CVE-2019-19629

CVE-2019-19629 is a high-severity vulnerability in Gitlab with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 1% (63rd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Gitlab
Published: 2020-01-05
Last modified: 2026-06-17

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.

Frequently asked questions

What is 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 via the Group Search API provided by the Elasticsearch integration.
How severe is CVE-2019-19629?: CVE-2019-19629 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2019-19629 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (63rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-19629?: CVE-2019-19629 affects Gitlab. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-19629?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2019-19629 published?: CVE-2019-19629 was published on 2020-01-05 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*

More vulnerabilities in Gitlab

CVE-2024-45409 — Critical (CVSS 10.0): The Ruby SAML library is for implementing the client side of a SAML authorization. Ruby-SAML in <= 12.2 and 1.13.0 <=…
CVE-2023-7028 — Critical (CVSS 10.0): An issue has been discovered in GitLab CE/EE affecting all versions from 16.1 prior to 16.1.6, 16.2 prior to 16.2.9,…
CVE-2023-2825 — Critical (CVSS 10.0): An issue has been discovered in GitLab CE/EE affecting only version 16.0.0. An unauthenticated malicious user can use a…
CVE-2022-0735 — Critical (CVSS 10.0): An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.10 before 14.6.5, all versions…
CVE-2021-22205 — Critical (CVSS 10.0): An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9. GitLab was not properly…
CVE-2019-9174 — Critical (CVSS 10.0): An issue was discovered in GitLab Community and Enterprise Edition before 11.6.10, 11.7.x before 11.7.6, and 11.8.x…

All CVEs affecting Gitlab →