dbcve.org
GitLabApplication

CVE-2025-4976

MEDIUM · 5.3 CVSS v3.1 Published 2025-07-24
Fix available
A fix is available. Upgrade to 18.0.5 / 18.1.3 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 EE affecting all versions from 17.0 before 18.0.5, 18.1 before 18.1.3, and 18.2 before 18.2.1 that, under certain circumstances, could have allowed an attacker to access internal notes in GitLab Duo responses.

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

This is an information disclosure vulnerability in GitLab EE where improper access controls on internal notes within GitLab Duo responses allow unauthorized access. An attacker could potentially view internal notes that should be restricted.

MitigationUpgrade GitLab EE to version 18.0.5 or later, 18.1.3 or later, or 18.2.1 or later to patch this vulnerability.

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:>= 17.0.0, < 18.0.5>= 18.1.0, < 18.1.3= 18.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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

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

  1. Determine installed GitLab version
    Run 'gitlab-rake gitlab:env:info' or check the version file at /opt/gitlab/version. Alternatively, visit Admin Area > Metrics and Profiling > Version on the web UI.
    Affected if The installed version falls within any of these ranges: >= 17.0.0 and < 18.0.5, OR >= 18.1.0 and < 18.1.3, OR exactly 18.2.
  2. Verify if GitLab Duo is enabled
    Check the GitLab Rails console for Duo configuration, or navigate to Admin Area > GitLab Duo in the web UI to confirm Duo features are active.
    Affected if GitLab Duo features are enabled and the installed version is vulnerable as determined in step 1.
  3. Audit access to internal notes in Duo responses
    Review API access logs or audit logs for requests to AI-powered Duo endpoints that return internal notes. Check if unauthorized users (non-project members, non-authors) can access notes marked as internal.
    Affected if Evidence exists that users outside the intended access scope can view internal notes through GitLab Duo response interfaces.

You are affected if your GitLab EE version is 17.0.0 through 18.0.4, 18.1.0 through 18.1.2, or exactly 18.2, AND you have GitLab Duo features enabled in your environment.

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.0.5 / 18.1.3 or later
Fixed in 18.0.518.1.3
Interim mitigation

Upgrade GitLab EE to version 18.0.5 or later, 18.1.3 or later, or 18.2.1 or later to patch this vulnerability.

Recommended fix High confidence

Upgrade to GitLab 18.0.5, 18.1.3, 18.2.1 or later

  1. 1. Back up your GitLab instance data and configuration before proceeding with the upgrade
  2. 2. Update your GitLab package repository to fetch the latest available packages
  3. 3. For Omnibus installations: run 'sudo apt-get update' and 'sudo apt-get install gitlab-ce' (or 'gitlab-ee')
  4. 4. For source installations: follow the upgrade path in the GitLab installation guide for your specific version
  5. 5. Run 'sudo gitlab-ctl reconfigure' to apply configuration changes
  6. 6. Run 'sudo gitlab-rake db:migrate' to ensure database migrations are applied
  7. 7. Verify the upgrade by checking the GitLab version at Admin Area > Settings > General > GitLab version
Caveat Review GitLab 18.x release notes for any behavior changes or required migration steps before upgrading

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
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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