CVE-2026-8280: DoS in GitLab 8.3 - 18.11.3
Platform
gitlab
Component
gitlab
Fixed in
18.11.3
CVE-2026-8280 describes a denial-of-service (DoS) vulnerability discovered in GitLab Community Edition (CE) and Enterprise Edition (EE). This flaw allows an authenticated user to trigger excessive memory consumption within the GitLab instance, potentially leading to service instability and unavailability. The vulnerability impacts versions 8.3 up to and including 18.11.3, with a fix available in version 18.11.3.
Impact and Attack Scenarios
An attacker exploiting CVE-2026-8280 could leverage a crafted input to exhaust GitLab's memory resources. This can manifest as a complete service outage, preventing legitimate users from accessing the platform. The impact is particularly severe in production environments where GitLab is critical for code management and collaboration. While the vulnerability requires authentication, a compromised user account or a user with sufficient privileges could be exploited to cause significant disruption. The memory exhaustion could also indirectly impact other processes running on the same server, potentially affecting related services.
Exploitation Context
CVE-2026-8280 was published on May 14, 2026. Its severity is currently assessed as medium (CVSS 6.5). There are no public exploits or active campaigns reported at this time. The vulnerability is not currently listed on KEV or EPSS, indicating a low probability of immediate exploitation. Monitor security advisories and threat intelligence feeds for any changes in the exploitation landscape.
Threat Intelligence
Exploit Status
CISA SSVC
CVSS Vector
What do these metrics mean?
- Attack Vector
- Network — remotely exploitable over the internet. No physical or local access required. Widest attack surface.
- Attack Complexity
- Low — no special conditions required. Attacker can exploit reliably without depending on rare configurations or timing.
- Privileges Required
- Low — any valid user account is sufficient. Basic authenticated access required.
- User Interaction
- None — attack is automatic and silent. Victim does nothing: no click, no file open.
- Scope
- Unchanged — impact is limited to the vulnerable component itself.
- Confidentiality
- None — no confidentiality impact. Attacker cannot read protected data.
- Integrity
- None — no integrity impact. Attacker cannot modify data.
- Availability
- High — complete crash or resource exhaustion. Full denial of service.
Affected Software
Weakness Classification (CWE)
Timeline
- Reserved
- Published
Mitigation and Workarounds
The primary mitigation for CVE-2026-8280 is to upgrade GitLab to version 18.11.3 or later. If immediate upgrading is not feasible, consider implementing temporary workarounds such as rate limiting on specific API endpoints or restricting user input sizes. Monitoring GitLab's memory usage is also crucial to detect potential exploitation attempts. Review user permissions and ensure least privilege principles are enforced to limit the potential impact of a compromised account. After upgrading, confirm the fix by attempting to trigger the vulnerable input and verifying that memory consumption remains within acceptable limits.
How to fix
Actualice GitLab a la versión 18.9.7 o superior, 18.10.6 o superior, o 18.11.3 o superior para mitigar la vulnerabilidad de denegación de servicio. Esta actualización aborda la falta de validación de entrada que permitía un consumo excesivo de memoria.
Frequently asked questions
What is CVE-2026-8280 — DoS in GitLab 8.3 - 18.11.3?
CVE-2026-8280 is a denial-of-service vulnerability in GitLab CE/EE versions 8.3 through 18.11.3. An authenticated user can trigger excessive memory consumption, potentially causing service disruption.
Am I affected by CVE-2026-8280 in GitLab 8.3 - 18.11.3?
You are affected if you are running GitLab CE/EE versions 8.3 through 18.11.3. Upgrade to version 18.11.3 or later to mitigate the vulnerability.
How do I fix CVE-2026-8280 in GitLab 8.3 - 18.11.3?
Upgrade GitLab to version 18.11.3 or later. Consider temporary workarounds like rate limiting if immediate upgrading is not possible.
Is CVE-2026-8280 being actively exploited?
Currently, there are no reports of active exploitation or public exploits for CVE-2026-8280, but monitoring is still recommended.
Where can I find the official GitLab advisory for CVE-2026-8280?
Refer to the official GitLab security advisory for CVE-2026-8280 on the GitLab website: [https://gitlab.com/security/advisories/](https://gitlab.com/security/advisories/)
Is your project affected?
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Try it now — no account
Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.
Drag & drop your dependency file
composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...