GitLabApplication
CVE-2025-13611
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGitLab 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn information disclosure vulnerability in GitLab CE/EE allowed authenticated users with access to certain log files to obtain sensitive tokens that were being logged under specific conditions. The issue affected versions from 13.2 before 18.5.5 and 18.6 before 18.6.3.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GitLabApplication
>= 13.2.0, < 18.4.5>= 18.5.0, < 18.5.3= 18.6.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine GitLab versionRun `sudo gitlab-rake gitlab:env:info` or check /opt/gitlab/version to obtain the installed GitLab versionAffected if The installed version falls within >= 13.2.0, < 18.4.5; >= 18.5.0, < 18.5.3; or equals 18.6.0
-
Identify log file locationsCheck the GitLab log directory (typically /var/log/gitlab) and identify log files such as production.log, api_json.log, or gitlab-rails/production.json.logAffected if Log files exist and are accessible to authenticated users beyond intended administrators
-
Inspect log files for sensitive tokensSearch log files for patterns matching tokens, API keys, or secret values using grep for strings like 'token=', 'secret', 'private_token', or 'VARIABLE' appearing in log entriesAffected if Log files contain any exposed sensitive tokens, API keys, or secret values that should not have been logged
-
Verify user access to log filesReview file permissions on /var/log/gitlab/ and subdirectories to determine if non-admin authenticated users have read access to log filesAffected if Authenticated users with limited privileges can read log files containing sensitive information
You are affected if your GitLab version is within the vulnerable range AND log files containing sensitive tokens are accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped18.4.518.5.3
Upgrade to GitLab 18.5.5, 18.6.3 or later. Review and restrict access to log files pending the upgrade.
18.5.5 or 18.6.3 (or later stable release)
- 1. Determine current GitLab version by checking /about or running `gitlab-rake gitlab:env:info`
- 2. If running version >= 13.2.0 and < 18.5.5, plan upgrade to version 18.5.5 or later
- 3. If running version >= 18.6.0 and < 18.6.3, plan upgrade to version 18.6.3 or later
- 4. Review GitLab upgrade prerequisites and backup documentation at docs.gitlab.com
- 5. Create a full backup before upgrading using `gitlab-backup-create`
- 6. Follow the official GitLab upgrade path for your current version at about.gitlab.com/upgradecenter/
- 7. After upgrade, verify the new version with `gitlab-rake gitlab:env:info`
- 8. Ensure log access controls are reviewed and limited to authorized personnel only
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13611 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13611 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data