Skip to main content

GitLab EUVDEUVD-2026-80122

| CVE-2026-1168 HIGH
Allocation of Resources Without Limits or Throttling (CWE-770)
2026-09-16 GitLab GHSA-8c2h-q92r-2j66
7.5
CVSS 3.1 · Vendor: GitLab
Share

Severity by source

Vendor (GitLab) PRIMARY
7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
7.5 HIGH

Unauthenticated GraphQL endpoint reachable over the network with a ready-made query technique, so PR:N/AV:N/AC:L; only availability is impacted.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (GitLab).

CVSS VectorVendor: GitLab

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

4
Metadata Corrected
Sep 16, 2026 - 07:40 vuln.today
tag: Graphql added
Patch available
Sep 16, 2026 - 07:01 EUVD
Analysis Generated
Sep 16, 2026 - 07:00 vuln.today
CVE Published
Sep 16, 2026 - 06:34 cve.org
HIGH 7.5

DescriptionCVE.org

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.4.6 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could have allowed an unauthenticated user to cause denial of service due to improper resource allocation limits in the GraphQL complexity calculation logic.

AnalysisAI

Unauthenticated denial of service in GitLab CE/EE (all versions from 18.4.6 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2) allows a remote attacker with no credentials to exhaust server resources through the GraphQL API by submitting queries whose true cost the complexity calculation under-counts. The flaw is an improper resource-allocation limit (CWE-770), scored CVSS 7.5 with the entire impact on availability (A:H) and none on confidentiality or integrity. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
technique details hidden
Delivery
technique details hidden
Exploit
technique details hidden
Execution
technique details hidden
Persist
technique details hidden
Impact
technique details hidden

Vulnerability AssessmentAI

Exploitation The prerequisite is a GitLab CE/EE instance running an affected version with its GraphQL API endpoint reachable by the attacker (normally /api/graphql, enabled by default and commonly exposed wherever the web UI is exposed). … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The signals here agree rather than conflict: CVSS 3.1 is 7.5 with AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, meaning a remote, unauthenticated, no-interaction attack with low complexity that degrades availability only - a textbook availability-flood profile rather than a data-breach profile, which is why the score stops at High instead of Critical. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario Full exploit scenario with step-by-step reproduction available after sign-in.
Remediation GitLab has released fixes in 19.1.8, 19.2.6, and 19.3.2, so the primary action is to upgrade to the appropriate patched release for your maintenance line - vendor-released patch: 19.3.2 (also 19.2.6 and 19.1.8) - following the instructions at https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-2-released/. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours, confirm which GitLab CE/EE instances fall in the affected ranges (18.4.6 up to but not including 19.1.8; 19.2 up to but not including 19.2.6; 19.3 up to but not including 19.3.2), prioritize internet-facing and partner-exposed instances, and apply rate limiting and request-size caps at the reverse proxy or WAF in front of the GraphQL endpoint while tightening any available GitLab administrator-configured GraphQL complexity, depth, and pagination limits to reduce the under-counted query cost gap; simultaneously enable alerting on CPU, memory, worker saturation, and GraphQL request latency so resource-exhaustion attempts are detected quickly. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

EUVD-2026-80122 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy