Allocation of Resources Without Limits or Throttling in GitLab

published 2026-02-11 8 mo ago modified 2026-09-08 2 mo ago also BIT-gitlab-2026-1456 , EUVD-2026-7048

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 37%
public exploits: 0; none known

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.7 before 18.7.4, and 18.8 before 18.8.4 that could have allowed an unauthenticated user to cause denial of service through CPU exhaustion by submitting specially crafted markdown files that trigger exponential processing in markdown preview.

Patch / fix

fixed in 2

bitnami gitlab 18.7.4, 18.8.4
GitLab GitLab 18.7.4, 18.8.4

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: partial
Assessed: 8 mo ago (2026-02-11)

Exploit prediction

0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

hackerone.com https://hackerone.com/reports/3517928 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
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
bitnami	gitlab	>=18.7.0, <18.7.4 >=18.8.0, <18.8.4	18.7.4 18.8.4

Affected products

GitLab GitLab

Classification

Weakness

CWE-770 Allocation of Resources Without Limits or Throttling

Technology feeds

GitLab rss critical rss

References

hackerone.com /reports/3517928
technical-description, exploit, permissions-required, web
about.gitlab.com /releases/2026/02/10/patch-release-gitlab-18-8-4-released/
release-notes, vendor-advisory, advisory
gitlab.com /gitlab-org/gitlab/-/issues/587688
issue-tracking, permissions-required, broken-link, report
nvd.nist.gov /vuln/detail/CVE-2026-1456
web

Sources

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.

Summary