Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By GitLab

  2. · 2 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-13611, by who scored it
Scored byCVSSScoreVector
GitLabCNA (assigner)3.1Low2.0CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N
NVDNVD · Modified3.1Medium5.3CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
0.27% · top 81% of all CVEs (20 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Low 2.0.

Affected products

  • GitLab · GitLab

    • affected 13.2 – < 18.5.5
    • affected 18.6 – < 18.6.3

What to do

Solution: Upgrade to versions 18.5.5, 18.6.3 or above.

References

References2

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-13611 badge
[![CVE-2025-13611](https://cveledger.app/badge/CVE-2025-13611.svg)](https://cveledger.app/cve/CVE-2025-13611)

Record last updated .