dbcve.org
GitLabApplication

CVE-2025-5819

MEDIUM · 5.0 CVSS v3.1 Published 2025-08-13
Fix available
A fix is available. Upgrade to 17.11.6 / 18.0.4 or later.
See remediation →
56/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 15.7 before 18.0.6, 18.1 before 18.1.4, and 18.2 before 18.2.2 that could have allowed authenticated users with developer access to obtain ID tokens for protected branches under certain circumstances.

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 confidence

Authenticated users with developer access to GitLab repositories could obtain ID tokens for protected branches under certain circumstances, representing a privilege escalation or authorization bypass issue in GitLab's branch protection mechanism.

MitigationUpgrade GitLab CE/EE to versions 18.0.6, 18.1.4, 18.2.2 or later to patch this authorization vulnerability affecting protected branch ID token issuance.

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:>= 15.7.0, < 17.11.6>= 18.0.0, < 18.0.4>= 18.1.0, < 18.1.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
Changed
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/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 checks

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

  1. Identify installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or check the GitLab admin panel under Help > Version. Alternatively, check `/opt/gitlab/version-manifest.json` or `cat /version` if using Omnibus installation.
    Affected if The installed version falls within the ranges: >= 15.7.0 and < 17.11.6, OR >= 18.0.0 and < 18.0.4, OR >= 18.1.0 and < 18.1.2.
  2. Check if protected branches exist
    Navigate to Project > Settings > Repository > Protected branches in the GitLab UI, or use the API: `GET /projects/:id/protected_branches` via curl with a personal access token.
    Affected if Protected branches are defined in the repository.
  3. Verify ID token generation is enabled for CI/CD pipelines
    Check project CI/CD settings under Settings > CI/CD > General pipelines. Look for the 'ID tokens' section or inspect the `.gitlab-ci.yml` file for `id_tokens:` configuration.
    Affected if ID tokens are enabled or configured in the pipeline settings or CI/CD configuration.
  4. Confirm developer or lower role access to the repository
    Review project members under Project > Settings > Members to identify users with Developer, Maintainer, or Reporter roles who have push or merge access to protected branches.
    Affected if Users with Developer or lower roles have access to pipelines that could trigger ID token generation for protected branches.

Your GitLab instance is affected if the installed version is vulnerable AND you have protected branches configured with ID tokens enabled, allowing authenticated developers to potentially obtain tokens for protected branches.

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 17.11.6 / 18.0.4 / 18.1.2 or later
Fixed in 17.11.618.0.418.1.2
Interim mitigation

Upgrade GitLab CE/EE to versions 18.0.6, 18.1.4, 18.2.2 or later to patch this authorization vulnerability affecting protected branch ID token issuance.

Recommended fix High confidence

Upgrade to 18.2.2 (or the latest 18.2.x release). For older branches: 17.11.6 for 17.x, 18.0.6 for 18.0.x, 18.1.4 for 18.1.x

  1. Identify your current GitLab version using gitlab-rake gitlab:env:info
  2. Review the GitLab upgrade path documentation for your current version
  3. Plan maintenance window - GitLab upgrades require downtime
  4. Backup your GitLab database and Git repositories
  5. Stop GitLab services before upgrade
  6. For GitLab installations: Use omnibus-gitlab to upgrade to the appropriate version
  7. For source installations: Follow the upgrade documentation to build from source
  8. After upgrade, verify GitLab is running: gitlab-rake gitlab:check
Caveat Standard GitLab upgrade considerations apply - review changelog for breaking changes between your current version and target version, particularly if skipping multiple minor versions

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5819 — 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-5819 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