dbcve.org
GitLabApplication

CVE-2026-0958

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 18.4 before 18.6.6, 18.7 before 18.7.4, and 18.8 before 18.8.4 that could have allowed an unauthenticated user to cause denial of service through memory or CPU exhaustion by bypassing JSON validation middleware limits.

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 vulnerability where unauthenticated users can bypass JSON validation middleware limits, allowing them to cause denial of service through memory or CPU exhaustion. The issue affects versions 18.4 through 18.6.5, 18.7.0 through 18.7.3, and 18.8.0 through 18.8.3.

MitigationUpgrade GitLab to version 18.6.6, 18.7.4, 18.8.4 or later to remediate this vulnerability. If immediate upgrading is not possible, consider implementing rate limiting at the load balancer or WAF level to mitigate unauthenticated requests.

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:>= 18.4.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:version` or access the Admin Area > Overview > Dashboard in the web UI to view the exact version number
    Affected if The installed version is >= 18.4.0 and < 18.6.6, OR >= 18.7.0 and < 18.7.4, OR >= 18.8.0 and < 18.8.4
  2. Verify unauthenticated API access is enabled
    Check if the GitLab instance allows unauthenticated access to JSON/API endpoints by reviewing the "Restricted visibility settings" in Admin Area > Settings > General > Visibility and access controls, or test public endpoints with a non-authenticated request
    Affected if Unauthenticated access to any JSON API endpoints is permitted (this is the default for public projects and many GitLab installations)
  3. Check for external rate limiting or WAF protection
    Inspect any upstream load balancer, reverse proxy, or web application firewall (WAF) configuration for rate limiting rules targeting JSON payload requests from unauthenticated sources
    Affected if No rate limiting or WAF is configured in front of GitLab to filter or throttle unauthenticated JSON requests

You are affected if your GitLab version falls within any of the vulnerable ranges AND unauthenticated users can reach your instance without upstream rate limiting protection.

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 to remediate this vulnerability. If immediate upgrading is not possible, consider implementing rate limiting at the load balancer or WAF level to mitigate unauthenticated requests.

Recommended fix Moderate confidence

18.8.4 or later (latest stable 18.x release)

  1. Backup your GitLab instance before starting the upgrade
  2. Review GitLab release notes for any known issues or breaking changes between your current and target version
  3. Ensure your system meets the requirements for the target GitLab version
  4. For Ubuntu/Debian: Run 'sudo apt-get update && sudo apt-get install gitlab-ee' or 'sudo apt-get install gitlab-ce' depending on your edition
  5. For RHEL/CentOS: Run 'sudo yum install gitlab-ee' or 'sudo yum install gitlab-ce' depending on your edition
  6. Run 'sudo gitlab-ctl reconfigure' after installation completes
  7. Verify GitLab is running: 'sudo gitlab-ctl status'
  8. Test that GitLab web interface is accessible and functional
Caveat Check GitLab 18.8 release notes for any breaking changes; minor version upgrades within 18.x typically have minimal breaking changes

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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