Authenticated service interruption through memory exhaustion
Published May 14, 2026 · Updated May 14, 2026
Resource exhaustion in GitLab CE/EE allows remote authenticated users to interrupt service over the network through excessive memory consumption. GitLab attributes the allocation to improper input validation but does not publicly identify the affected request, parameter, or code path. A low-privileged account is required; successful exploitation exhausts memory without reported data access or modification.
Summary
What happened
Resource exhaustion in GitLab CE/EE allows remote authenticated users to interrupt service over the network through excessive memory consumption. GitLab attributes the allocation to improper input validation but does not publicly identify the affected request, parameter, or code path. A low-privileged account is required; successful exploitation exhausts memory without reported data access or modification.
The record
- CVE
- CVE-2026-8280
- Published
- May 14, 2026
- Updated
- May 14, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-770, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2026CVE publishedPublication date reported by the CVE source.
- May 14, 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=18.10 <18.10.6
- Affected versionversion=18.11 <18.11.3
- Affected versionversion=8.3 <18.9.7
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