GitLab has fixed 12 vulnerabilities in both the Community Edition (CE) and Enterprise Edition (EE) versions. Among these, one vulnerability is rated as critical. The affected versions span from 7.0 up to certain 19.x releases. No CVSS score is provided for these vulnerabilities. There are no known exploits in the wild reported at this time.
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD configuration, due to insufficient regular expression validation.
A vulnerability in GitLab CE/EE versions from 18.3 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 allows an authenticated user with an MCP-scoped token to perform actions beyond the intended scope due to improper authorization checks. This issue has been remediated in versions 19.2.7, 19.3.3, and 19.4.1. The vulnerability has a medium severity rating with a CVSS score of 5.4.
A race condition vulnerability in GitLab CE/EE versions from 18.6 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 could cause the MCP search tool to return search results under an incorrect user context.
A vulnerability in GitLab CE/EE versions from 19.1 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 could allow an authenticated user to spoof merge request authorship and attribute content to arbitrary existing users due to improper reliance on ephemeral cache state during Direct Transfer imports. This issue has been remediated by GitLab.
GitLab has remediated an issue in GitLab EE affecting all versions from 18.3 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could allow an authenticated user with Duo Chat access to obtain Advanced Search instance configurations and sensitive credentials using a specially crafted GraphQL subscription argument to bypass serialization and perform server object lookup.
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API.
A vulnerability in GitLab CE/EE versions from 14.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 allows an attacker to execute arbitrary JavaScript in another user's browser via a crafted URL. This occurs due to improper sanitization of user-controlled input, leading to a cross-site scripting (XSS) issue. The vulnerability has been remediated in the specified fixed versions.
A vulnerability in GitLab CE/EE versions from 12.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 allows an authenticated user with Maintainer role to modify protected branch configurations due to improper authorization in a project API endpoint. This issue has been remediated by GitLab in the specified fixed versions.
A vulnerability in GitLab CE/EE versions from 10.6 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 allowed an authenticated user with developer-role permissions to commit changes to a project even after being removed as a member. This was due to improper authorization checks on merge request collaboration settings. The issue has been remediated in the specified fixed versions.
A vulnerability in GitLab CE/EE versions from 11.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 could allow an unauthenticated user to cause a denial of service. The issue arises from insufficient resource throttling when processing merge request discussions. This vulnerability has been remediated in the specified fixed versions.
An issue has been discovered in GitLab CE/EE affecting all versions from 16.0 prior to 16.6.6, 16.7 prior to 16.7.4, and 16.8 prior to 16.8.1 which allows an authenticated user to write files to arbitrary locations on the GitLab server while creating a workspace.