PatchSiren cyber security CVE debrief
CVE-2025-13761 GitLab CVE debrief
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.6 before 18.6.3, and 18.7 before 18.7.1 that could have allowed an unauthenticated user to execute arbitrary code in the context of an authenticated user's browser by convincing the legitimate user to visit a specially crafted webpage. This issue has been patched in GitLab versions 18.6.3 and 18.7.1. Users of affected versions should update to a patched version as soon as possible. The CVSS score for this vulnerability is 8, indicating a high severity. The vulnerability was publicly disclosed on January 9, 2026, and has since been modified on June 30, 2026.
- Vendor
- GitLab
- Product
- Unknown
- CVSS
- HIGH 8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-01-09
- Original CVE updated
- 2026-07-15
- Advisory published
- 2026-01-09
- Advisory updated
- 2026-07-15
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.
Sources and references
Verified primary and authoritative sources
-
CVE-2025-13761 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2025-13761
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2025-13761 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2025-13761
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Mitigation or vendor reference
Unverified legacy reference
URL: https://about.gitlab.com/releases/2026/01/07/patch-release-gitlab-18-7-1-released/
[email protected] - Release Notes, Vendor Advisory
-
Source reference
Unverified legacy reference
URL: https://gitlab.com/gitlab-org/gitlab/-/issues/582237
[email protected] - Broken Link
-
Source reference
Unverified legacy reference
URL: https://hackerone.com/reports/3441368
[email protected] - Permissions Required
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/security/cve/CVE-2025-13761
0b0ca135-0b70-47e7-9f44-1890c2a1c46c
-
Source reference
Unverified legacy reference
URL: https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-13761.json
0b0ca135-0b70-47e7-9f44-1890c2a1c46c
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.