GitLabApplication
CVE-2026-1092
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 · uneditedGitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.10 before 18.8.9, 18.9 before 18.9.5, and 18.10 before 18.10.3 that could have allowed an unauthenticated user to cause denial of service due to improper input validation of JSON payloads.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
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 confidenceGitLab CE/EE contains a denial of service vulnerability in versions 12.10 through 18.10.3 (before specific patched releases) where improper input validation of JSON payloads allows unauthenticated users to crash the service.
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
>= 12.10.0, < 18.8.9>= 18.9.0, < 18.9.5>= 18.10.0, < 18.10.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine if GitLab is installedRun `gitlab-rake gitlab:env:info` or check for GitLab processes with `ps aux | grep gitlab`Affected if GitLab is not found on the system
-
Get installed GitLab versionRun `gitlab-rake gitlab:git:version` or check the Admin Area > Settings > General page in the web UI for the version numberAffected if The version returned is not obtainable or shows no version
-
Compare version against affected rangesCompare your installed version to: < 18.8.9, >= 18.9.0 and < 18.9.5, or >= 18.10.0 and < 18.10.3. Also note versions prior to 12.10.0 are not covered by this CVE.Affected if Your version falls within any of these ranges: 12.10.0 to 18.8.8, 18.9.0 to 18.9.4, or 18.10.0 to 18.10.2
-
Verify GitLab is network accessibleCheck if the GitLab web interface or API is exposed to network traffic from untrusted sourcesAffected if GitLab is reachable from networks where unauthenticated attackers could send HTTP requests
You are affected if GitLab is running and the installed version falls within 12.10.0 to 18.10.2 (specifically <18.8.9, >=18.9.0 <18.9.5, or >=18.10.0 <18.10.3) and is network accessible to unauthenticated attackers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped18.8.918.9.518.10.3
Upgrade to GitLab version 18.8.9, 18.9.5, 18.10.3 or later. As this affects unauthenticated users, immediate prioritization is recommended.
GitLab 18.10.3 or later stable release (or 18.8.9/18.9.5 depending on your current branch)
- 1. Back up your current GitLab installation and database before upgrading.
- 2. Identify your current GitLab version by running `gitlab-rake gitlab:env:info` or checking the GitLab admin area.
- 3. Plan your upgrade path: if you are on 12.10.x through 18.7.x, upgrade to 18.8.9; if on 18.9.x, upgrade to 18.9.5; if on 18.10.x, upgrade to 18.10.3.
- 4. For the recommended path, upgrade directly to GitLab 18.10.3 or later stable release following official upgrade guides.
- 5. After upgrade, verify GitLab is running: `gitlab-rake gitlab:check` or check the admin dashboard.
- 6. Confirm the vulnerability is remediated by verifying the GitLab version matches a fixed release.
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
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1092 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-1092 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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