dbcve.org
GitLabApplication

CVE-2025-10094

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-12
Fix available
A fix is available. Upgrade to 18.1.6 / 18.2.6 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
An issue has been discovered in GitLab CE/EE affecting all versions from 10.7 before 18.1.6, 18.2 before 18.2.6, and 18.3 before 18.3.2 that could have allowed authenticated users to disrupt access to token listings and related administrative operations by creating tokens with excessively large names.

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 · high confidence

Authenticated GitLab users could create tokens with excessively large names, causing a denial of service on token listing pages and blocking administrative operations. This is an input validation vulnerability where the token name field lacks proper length constraints.

MitigationUpgrade GitLab to version 18.1.6, 18.2.6, 18.3.2 or later to implement token name length validation.

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
Affected:>= 10.7.0, < 18.1.6>= 18.2.0, < 18.2.6>= 18.3.0, < 18.3.2

CVSS 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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check `/opt/gitlab/version` to obtain the exact installed version number
    Affected if The installed version falls within >= 10.7.0 and < 18.1.6, OR >= 18.2.0 and < 18.2.6, OR >= 18.3.0 and < 18.3.2
  2. Identify token creation capability
    Determine if authenticated users have access to create personal access tokens or session tokens in the GitLab instance
    Affected if User authentication and token creation features are enabled and accessible to non-admin users
  3. Check for token listing behavior
    Navigate to User Settings -> Access Tokens or the admin area Tokens page and observe loading performance
    Affected if Token listing pages load slowly, timeout, or cause high server load when accessed
  4. Review token records in database
    Query the database for tokens with unusually long name fields (e.g., names exceeding several hundred characters) using: `SELECT id, user_id, name, LENGTH(name) as name_length FROM personal_access_tokens WHERE LENGTH(name) > 500;`
    Affected if Tokens exist with name fields exceeding typical length limits (e.g., > 500 characters)

The environment is affected if running a GitLab version in the vulnerable ranges AND users can create tokens AND tokens with excessively long names exist in the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 18.1.6 / 18.2.6 / 18.3.2 or later
Fixed in 18.1.618.2.618.3.2
Interim mitigation

Upgrade GitLab to version 18.1.6, 18.2.6, 18.3.2 or later to implement token name length validation.

Recommended fix High confidence

Upgrade to GitLab 18.3.2 or later (or 18.2.6 if staying on 18.2.x, or 18.1.6 if staying on 18.1.x)

  1. 1. Back up the GitLab database and configuration files before proceeding with the upgrade.
  2. 2. Update your package repository and install the latest GitLab package.
  3. 3. Run 'gitlab-ctl reconfigure' to apply the configuration changes.
  4. 4. Verify the upgrade was successful by checking the GitLab version at Admin Area > Settings > Metrics and profiling > Version.
Caveat Standard GitLab upgrade considerations apply - review the release notes for any between-version migrations or breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10094 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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