CVE-2019-6995 json
An issue was discovered in GitLab Community and Enterprise Edition 8.x, 9.x, 10.x, and 11.x before 11.5.8, 11.6.x before 11.6.6, and 11.7.x…
published 7y ago modified 4mo ago also EUVD-2019-16546
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
An issue was discovered in GitLab Community and Enterprise Edition 8.x, 9.x, 10.x, and 11.x before 11.5.8, 11.6.x before 11.6.6, and 11.7.x before 11.7.1. It has Incorrect Access Control. Users are able to comment on locked project issues.
Patch / fix
- gitlab gitlab 11.5.8, 11.6.6, 11.7.1
Is CVE-2019-6995 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
0.83% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- gitlab.com https://gitlab.com/gitlab-org/gitlab-ce/issues/55537 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-281 Improper Preservation of Permissions
- Technology feeds
References
-
gitlab.com
/gitlab-org/gitlab-ce/issues/55537
exploit, issue-tracking, third-party-advisory
-
about.gitlab.com
/2019/01/31/security-release-gitlab-11-dot-7-dot-3-released/
release-notes, vendor-advisory
Sources
- CVE List CVE-2019-6995
- NVD CVE-2019-6995
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.