dbcve.org
GitLabApplication

CVE-2025-1477

HIGH · 7.5 CVSS v3.1 Published 2025-08-13
Fix available
A fix is available. Upgrade to 18.0.6 / 18.1.4 or later.
See remediation →
84/100
Remediation priority · High
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 CE/EE affecting all versions from 8.14 before 18.0.6, 18.1 before 18.1.4, and 18.2 before 18.2.2 that could have allowed an unauthenticated user to create a denial of service condition by sending specially crafted payloads to specific integration API endpoints.

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

An unauthenticated remote denial of service vulnerability in GitLab CE/EE allows attackers to send specially crafted payloads to specific integration API endpoints, causing service disruption. The vulnerability affects versions from 8.14 through 18.0.5, 18.1.0-18.1.3, and 18.2.0-18.2.1.

MitigationUpgrade GitLab to version 18.0.6, 18.1.4, or 18.2.2 or later to patch the vulnerability. As a defensive measure, consider restricting external access to integration API endpoints via firewall or authentication proxies until the upgrade is completed.

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:>= 8.1.4, < 18.0.6>= 18.1.0, < 18.1.4>= 18.2.0, < 18.2.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine installed GitLab version
    Run 'sudo gitlab-rake gitlab:version' or check /opt/gitlab/version on the GitLab server
    Affected if The version falls within 8.14 through 18.0.5, 18.1.0-18.1.3, or 18.2.0-18.2.1 (or equivalently: >= 8.1.4 and < 18.0.6, or >= 18.1.0 and < 18.1.4, or >= 18.2.0 and < 18.2.2)
  2. Verify integration API endpoint exposure
    Review web server or firewall configuration to determine if integration API endpoints (such as /api/v4/integrations/*) are reachable from untrusted networks
    Affected if Integration API endpoints are accessible from the internet or untrusted internal networks without authentication
  3. Check external access to GitLab instance
    Confirm whether the GitLab web interface is exposed directly to the internet or accessible without authentication via reverse proxy
    Affected if The GitLab instance accepts unauthenticated HTTP/HTTPS connections from external sources
  4. Identify enabled integrations
    Review which integration modules are enabled in GitLab admin settings under /admin/integrations, or query the API at /api/v4/integrations with admin credentials
    Affected if Any third-party integrations are enabled and their API endpoints are externally accessible

A user is affected if their GitLab version is within the vulnerable ranges AND the integration API endpoints are accessible to unauthenticated or external attackers.

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.6 / 18.1.4 / 18.2.2 or later
Fixed in 18.0.618.1.418.2.2
Interim mitigation

Upgrade GitLab to version 18.0.6, 18.1.4, or 18.2.2 or later to patch the vulnerability. As a defensive measure, consider restricting external access to integration API endpoints via firewall or authentication proxies until the upgrade is completed.

Recommended fix High confidence

Upgrade to GitLab 18.2.2 or later (latest stable release recommended)

  1. 1. Back up your GitLab instance data before proceeding with the upgrade
  2. 2. Review the GitLab upgrade documentation for your installation method (omnibus, source, or Docker)
  3. 3. Plan for appropriate downtime during the upgrade process
  4. 4. For Omnibus installations: run 'apt-get update && apt-get install gitlab-ce' or 'yum install gitlab-ce' depending on your OS
  5. 5. For Docker installations: pull and run the latest image with the fixed version tag (e.g., gitlab/gitlab-ee:18.2.2
  6. 6. After upgrade, verify GitLab is running: gitlab-rake gitlab:health
  7. 7. Test that integration API endpoints are functioning correctly
Caveat Review GitLab release notes for 18.2.x series for any breaking changes between your current version and the target version

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

Fix this in GitLab Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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