dbcve.org
GitLabApplication

CVE-2026-1458

HIGH · 7.5 CVSS v3.1 Published 2026-02-11
Fix available
A fix is available. Upgrade to 18.6.6 / 18.7.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
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.0 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that, under certain conditions could have allowed an unauthenticated user to cause denial of service by uploading malicious files.

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

GitLab CE/EE contains a denial of service vulnerability where an unauthenticated attacker can upload malicious files that cause service disruption. The vulnerability affects all versions from 8.0 through 18.6.5, 18.7.x before 18.7.4, and 18.8.x before 18.8.4.

MitigationUpgrade GitLab to version 18.6.6, 18.7.4, 18.8.4 or later. Until upgraded, consider restricting unauthenticated file upload functionality at the network level.

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.0.0, < 18.6.6>= 18.7.0, < 18.7.4>= 18.8.0, < 18.8.4

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. Check installed GitLab version
    Run `sudo gitlab-rake gitlab:env:info` or `curl -s https://your-gitlab-instance/api/v4/version` to retrieve the running version number
    Affected if The version falls within 8.0.0 to 18.6.5, 18.7.0 to 18.7.3, or 18.8.0 to 18.8.3
  2. Verify unauthenticated access is enabled
    Navigate to the GitLab login page from a private/incognito browser window without providing credentials. Confirm whether the page loads and shows options like 'Register' or allows access to public projects without signing in
    Affected if Unauthenticated users can access the GitLab instance without any login requirement
  3. Check public project and file upload exposure
    Visit public project URLs or attempt to access the API endpoint `curl -s https://your-gitlab-instance/api/v4/projects` without authentication headers
    Affected if Project data or file upload interfaces are reachable by unauthenticated users

If the installed version is within the vulnerable ranges AND unauthenticated users can access the instance or upload files, the environment is affected by this CVE.

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.6.6 / 18.7.4 / 18.8.4 or later
Fixed in 18.6.618.7.418.8.4
Interim mitigation

Upgrade GitLab to version 18.6.6, 18.7.4, 18.8.4 or later. Until upgraded, consider restricting unauthenticated file upload functionality at the network level.

Recommended fix High confidence

GitLab 18.8.4 (or latest 18.x stable)

  1. 1. Back up your GitLab instance database and repositories before starting the upgrade.
  2. 2. Review the GitLab upgrade path documentation for your current version to ensure you follow a compatible upgrade sequence.
  3. 3. For major version jumps (e.g., from 8.x to 18.x), consider upgrading through intermediate major versions as recommended by GitLab's documentation.
  4. 4. Download and install the fixed version: upgrade to GitLab 18.8.4 (or the latest 18.x stable release) from gitlab.com or your package manager.
  5. 5. After upgrade, verify that GitLab services are running properly: sudo gitlab-ctl status
  6. 6. Test that file upload functionality works correctly and the DoS vulnerability is mitigated.
Caveat Major version upgrades (especially from 8.x/9.x to 18.x) may require database migrations and configuration changes; review GitLab upgrade guides for breaking changes between your current and target version

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
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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