BaseFortify

Publication date: 2025-11-26

Last updated on: 2026-03-31

Assigner: GitLab Inc.

Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.2 before 18.5.5 and 18.6 before 18.6.3 that could have allowed an authenticated user with access to certain logs to obtain sensitive tokens under specific conditions.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-11-26

Last Modified

2026-03-31

Generated

2026-07-07

AI Q&A

2025-11-26

EPSS Evaluated

2026-07-05

NVD

CVE-2025-13611

Affected Vendors & Products

Vendor	Product	Version / Range
gitlab	gitlab	From 13.2.0 (inc) to 18.4.5 (exc)
gitlab	gitlab	From 13.2.0 (inc) to 18.4.5 (exc)
gitlab	gitlab	From 18.5.0 (inc) to 18.5.3 (exc)
gitlab	gitlab	From 18.5.0 (inc) to 18.5.3 (exc)
gitlab	gitlab	18.6.0
gitlab	gitlab	18.6.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-532	The product writes sensitive information to a log file.

Attack-Flow Graph

Executive Summary

This vulnerability in GitLab CE/EE versions before certain fixed releases could allow an authenticated user with access to specific logs to obtain sensitive tokens under certain conditions.

Impact Analysis

An attacker who is an authenticated user with access to certain logs could potentially obtain sensitive tokens, which might lead to unauthorized access or misuse of those tokens.

Mitigation Strategies

To mitigate this vulnerability, update GitLab CE/EE to a fixed version: 18.4.5 or later for 18.4.x, 18.5.3 or later for 18.5.x, and 18.6.1 or later for 18.6.x. Restrict access to logs to only trusted users and review permissions for authenticated users to limit exposure to sensitive tokens.

Hi! I’m here to help you understand CVE-2025-13611. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70