CVE-2026-82837
MediumCVSS 5.3Summary
GitLab CE/EE has an improper authorization issue on internal data emission endpoints that, under certain conditions, allows an authenticated user to access sensitive credentials and tokens without transiting the expected proxy. Affected versions are from 10.1.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2.
Risk Assessment
An authenticated user could access sensitive credentials and tokens, potentially leading to privilege escalation or unauthorized access to other systems.
Recommendation
Update GitLab CE/EE to version 19.1.8, 19.2.6, or 19.3.2 (or later) and review access logs for internal endpoints.
Other vulnerabilities in GitLab CE/EE
See all- CVE-2026-8030Medium
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could have allowed an authenticated user to prevent another user from modifying their group settings due to improper validation of group URL slugs during namespace transfers.
- CVE-2026-7514Medium
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.9 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that an authenticated user with developer-role permissions could substitute package file content and hide packages from their owners due to improper authorization checks in the Generic Package Registry.
- CVE-2026-13210High
GitLab CE/EE versions from 15.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 contain a vulnerability that under certain conditions allows an authenticated user to access CI/CD variables outside their intended environment scope. The cause is improper input validation in the environment scope pattern matcher.
- CVE-2026-1659High
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.0 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3. This issue could have allowed an unauthenticated user to cause denial of service by sending specially crafted requests due to insufficient input validation.
- CVE-2025-14870High
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.5 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3. This issue could have allowed an unauthenticated user to cause denial of service by sending specially crafted JSON payloads due to insufficient input validation.
- CVE-2025-14869High
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.5 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3. This issue could have allowed an unauthenticated user to cause denial of service by sending specially crafted payloads on certain API endpoints.
- CVE-2023-3364High
An issue has been discovered in GitLab CE/EE affecting all versions from 8.14 before 16.0.8, from 16.1 before 16.1.3, and from 16.2 before 16.2.2. A Denial of Service (DoS) attack was possible via crafted payloads using AutolinkFilter at the preview_markdown endpoint.
- CVE-2026-6336Medium
A missing authorization check in GitLab CE/EE allows an unauthorized user to view project import source information. Affected versions are from 16.6 to 19.0.4, 19.1 to 19.1.2, and 19.2 to 19.2.0.
- CVE-2025-14562Low
GitLab CE/EE has improper authorization checks on merge request collaboration settings, allowing an authenticated user with developer role to commit changes to a project after being removed as a member. Affected versions are 10.6 through 19.0.4, 19.1 through 19.1.2, and 19.2 through 19.2.0.
- CVE-2026-2238Medium
A vulnerability in GitLab CE/EE allowed an unauthenticated user to view confidential issue references in public projects under certain conditions due to improper authorization checks. Affected versions: 17.5 to 18.11.6, 19.0 to 19.0.3, and 19.1 to 19.1.1.
Original NVD description (English source)
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.1.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that certain conditions could have allowed an authenticated user to access sensitive credentials and tokens without transiting the expected proxy due to improper authorization checks on internal data emission endpoints.

