dbcve.org
GitLabApplication

CVE-2025-7449

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-26
Fix available
A fix is available. Upgrade to 18.4.5 / 18.5.3 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
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.3 before 18.4.5, 18.5 before 18.5.3, and 18.6 before 18.6.1 that could have allowed an authenticated user with specific permissions to cause a denial of service condition through HTTP response processing.

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

A denial of service vulnerability exists in GitLab CE/EE affecting versions 8.3 through 18.4.4, 18.5.0-18.5.2, and 18.6.0. An authenticated user with specific permissions can trigger the vulnerability through malicious HTTP response processing, causing the service to become unavailable.

MitigationUpgrade GitLab to version 18.4.5, 18.5.3, 18.6.1 or later to remediate 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:>= 8.3.0, < 18.4.5>= 18.5.0, < 18.5.3= 18.6.0

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. Identify installed GitLab version
    Run command: gitlab-rake gitlab:env:info or check /opt/gitlab/embedded/service/gitlab-rails/VERSION file. Alternatively, visit Admin Area > Dashboard > Overview and read the GitLab version displayed.
    Affected if Version falls within >= 8.3.0 and < 18.4.5, OR >= 18.5.0 and < 18.5.3, OR equals 18.6.0
  2. Confirm GitLab edition and installation type
    Check if running GitLab CE or EE. Run: gitlab-rake gitlab:env:info | grep -i edition. This CVE affects both Community Edition and Enterprise Edition.
    Affected if Running CE or EE edition within the affected version ranges from step 1
  3. Verify authentication is enabled
    Confirm the GitLab instance allows user authentication. By default, GitLab requires authentication for users. Check Admin Area > Settings > General > Sign-up restrictions to see if sign-up is enabled or if external authentication is configured.
    Affected if User authentication is permitted on the instance (default state for most GitLab deployments)
  4. Check for unusual service availability issues
    Review GitLab logs for DoS indicators: grep -i 'error' /var/log/gitlab/gitlab-rails/production.log | tail -100. Look for patterns related to HTTP response processing failures or service crashes around the time of suspected exploitation.
    Affected if Service has experienced unexplained unavailability or crashes linked to authenticated user activity

The environment is affected if GitLab version is 8.3.0 through 18.4.4, 18.5.0 through 18.5.2, or exactly 18.6.0, and the instance permits authenticated user access.

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.4.5 / 18.5.3 or later
Fixed in 18.4.518.5.3
Interim mitigation

Upgrade GitLab to version 18.4.5, 18.5.3, 18.6.1 or later to remediate this vulnerability.

Recommended fix High confidence

18.4.5 (or latest 18.4.x), 18.5.3 (or latest 18.5.x), or 18.6.1 (or latest 18.6.x) depending on current version

  1. 1. Identify the currently running GitLab version using `gitlab-rake gitlab:version` or the admin dashboard.
  2. 2. Determine the appropriate upgrade path based on current version: if running 17.x or earlier, upgrade to 18.4.5; if running 18.4.x, upgrade to 18.4.5 or later; if running 18.5.x, upgrade to 18.5.3 or later; if running 18.6.0, upgrade to 18.6.1 or later.
  3. 3. Create a full backup of the GitLab instance using `gitlab-backup-create` or the admin backup interface.
  4. 4. Review the official GitLab upgrade documentation for your installation method (Omnibus, source, or Helm chart).
  5. 5. For Omnibus installations: run `sudo apt-get update && sudo apt-get install gitlab-ee` (or gitlab-ce) to upgrade to the latest patch version in your current minor series, or specify the target version.
  6. 6. For source installations: stop GitLab services, fetch the new version tags, checkout the fixed release (e.g., v18.4.5), run database migrations with `bundle exec rake db:migrate`, and restart services.
  7. 7. Verify the upgrade was successful by checking the version in the admin area and confirming all services are running.
  8. 8. Test critical functionality (project creation, user authentication, repository access) to ensure the upgrade did not introduce regressions.
Caveat Patch releases typically contain only bug fixes and security patches with minimal risk of breaking changes; however, always review the CHANGELOG for the target version before upgrading

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-7449 — 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-7449 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