CVE-2019-9219

LOWNVD 3.73.7—Trending — 3 sources updated this week

3.7

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 before 11.8.1. It has Incorrect Access Control (issue 2 of 5).

CVSS v3: 3.7
EG Score: 3.7(medium)
EPSS: 36.5%
KEV: Not listed

Published

April 17, 2019

Last Modified

November 21, 2024

References (6)

cve@mitrehttps://about.gitlab.com/2019/03/04/security-release-gitlab-11-dot-8-dot-1-released/
cve@mitrehttps://about.gitlab.com/blog/categories/releases/
cve@mitrehttps://gitlab.com/gitlab-org/gitlab-ce/issues/54159
af854a3a-2127-422b-91ae-364da2661108https://about.gitlab.com/2019/03/04/security-release-gitlab-11-dot-8-dot-1-released/
af854a3a-2127-422b-91ae-364da2661108https://about.gitlab.com/blog/categories/releases/
af854a3a-2127-422b-91ae-364da2661108https://gitlab.com/gitlab-org/gitlab-ce/issues/54159

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-639Authorization Bypass Through User-Controlled Key (IDOR)

Data Freshness Timeline

(refreshed 13× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 20:30 UTCEG score recompute
2026-05-27 20:30 UTCGHSA enrichment
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-24 16:47 UTCepss_batch

Frequently asked(5)

What is CVE-2019-9219?

CVE-2019-9219 is a low vulnerability published on April 17, 2019. 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 before 11.8.1. It has Incorrect Access Control (issue 2 of 5).

When was CVE-2019-9219 disclosed?

CVE-2019-9219 was first published in the National Vulnerability Database on April 17, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2019-9219 actively exploited?

CVE-2019-9219 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 36.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2019-9219?

CVE-2019-9219 has a CVSS v3 base score of 3.7 (NVD).

How do I remediate CVE-2019-9219?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-9219, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-9219

Explore →

Is Your Infrastructure Affected by CVE-2019-9219?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2019-9219

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-9219?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)