Authenticated service interruption via unbounded GraphQL resources
Published Apr 22, 2026 · Updated Apr 22, 2026
Resource exhaustion in affected GitLab CE/EE releases from 12.4 through 18.11 allows remote authenticated users to interrupt service through GraphQL. The GraphQL API applies insufficient resource-allocation limits, allowing authenticated requests to consume enough server resources to overwhelm the instance. Valid credentials and network access to the API are required; the published impact is limited to service availability.
Summary
What happened
Resource exhaustion in affected GitLab CE/EE releases from 12.4 through 18.11 allows remote authenticated users to interrupt service through GraphQL. The GraphQL API applies insufficient resource-allocation limits, allowing authenticated requests to consume enough server resources to overwhelm the instance. Valid credentials and network access to the API are required; the published impact is limited to service availability.
The record
- CVE
- CVE-2025-3922
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=12.4 <18.9.6
- Affected versionversion=18.10 <18.10.4
- Affected versionversion=18.11 <18.11.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo