CVE-2026-8280 json
Allocation of Resources Without Limits or Throttling in GitLab
published 2026-05-14 5 mo ago modified 2026-09-08 2 mo ago also BIT-gitlab-2026-8280 , EUVD-2026-30243
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.3 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user to cause denial of service through excessive memory consumption due to improper input validation.
Patch / fix
- bitnami gitlab 18.9.7, 18.10.6, 18.11.3
- GitLab GitLab 18.9.7, 18.10.6, 18.11.3
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- hackerone.com https://hackerone.com/reports/3329085 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | gitlab | >=8.3.0, <18.9.7 >=18.10.0, <18.10.6 >=18.11.0, <18.11.3 |
18.9.7 18.10.6 18.11.3 |
Affected products
- GitLab GitLab
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
- Technology feeds
References
-
hackerone.com
/reports/3329085
technical-description, exploit, permissions-required, web
-
gitlab.com
/gitlab-org/gitlab/-/work_items/579035
broken-link, web
-
about.gitlab.com
/releases/2026/05/13/patch-release-gitlab-18-11-3-released/
release-notes, article
-
nvd.nist.gov
/vuln/detail/CVE-2026-8280
web
Sources
- CVE List CVE-2026-8280
- NVD CVE-2026-8280
- OSV BIT-gitlab-2026-8280
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.