CVE-2025-13761 GitLab CVE debrief

Who should care

Administrators and users of GitLab CE/EE versions 18.6 before 18.6.3 and 18.7 before 18.7.1 should be aware of this vulnerability and take immediate action to update to a patched version. Additionally, security teams and vulnerability managers should be aware of the potential impact of this vulnerability and prioritize patching accordingly.

Technical summary

The vulnerability in GitLab CE/EE allows an unauthenticated user to execute arbitrary code in the context of an authenticated user's browser. This is achieved by convincing the legitimate user to visit a specially crafted webpage. The issue affects all versions from 18.6 before 18.6.3 and 18.7 before 18.7.1. The CVSS vector for this vulnerability is CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N, indicating a high severity. The weakness associated with this vulnerability is CWE-79.

Defensive priority

High priority should be given to patching GitLab CE/EE versions 18.6 before 18.6.3 and 18.7 before 18.7.1. Administrators should update to versions 18.6.3 or 18.7.1 as soon as possible to mitigate the risk of arbitrary code execution.

Recommended defensive actions

• Update GitLab CE/EE to version 18.6.3 or 18.7.1
• Review and apply patches provided by GitLab
• Monitor GitLab instances for suspicious activity
• Restrict access to sensitive areas of the GitLab instance
• Implement additional security measures to detect and prevent similar vulnerabilities

Evidence notes

The vulnerability was publicly disclosed on January 9, 2026, and has since been modified on June 30, 2026. The CVSS score for this vulnerability is 8, indicating a high severity. The weakness associated with this vulnerability is CWE-79. The vulnerability affects all versions from 18.6 before 18.6.3 and 18.7 before 18.7.1.

Official resources