GitLab · GitLab · published 2025-11-26

CVE-2025-13611Insertion of Sensitive Information into Log File in GitLab

Routine No exploitation evidence; EPSS 0.3%.

CVE-2025-13611 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 19% of all CVEs. This GitLab vulnerability: CVSS 2.0 (v3.1). Fixed upstream in GitLab 18.6.1, 18.5.3, 18.4.5. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in GitLab 18.6.1, 18.5.3, 18.4.5.

Patch events

  1. This monthSecurity release

    DevOpsGitLab

    GitLab security releases: 18.6.1, 18.5.3, 18.4.5

    Upgrade to 18.6.118.5.318.4.5

    Why: Vendor security release for server software (most severe: CVE-2024-9183).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.3% (19th pct)FIRST EPSS v2026.06.15
CVSS base score2.0 (v3.1)
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →