GitLab Community Edition/Enterprise Edition up to 18.7.5/18.8.5/18.9.1 Webhook allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in GitLab Community Edition and Enterprise Edition up to 18.7.5/18.8.5/18.9.1. The impacted element is an unknown function of the component Webhook Handler. Executing a manipulation can lead to allocation of resources. The identification of this vulnerability is CVE-2025-12576. The attack may be launched remotely. There is no exploit available. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic was found in GitLab Community Edition and Enterprise Edition up to 18.7.5/18.8.5/18.9.1. This vulnerability affects an unknown function of the component Webhook Handler. The manipulation with an unknown input leads to a allocation of resources vulnerability. The CWE definition for the vulnerability is CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. As an impact it is known to affect availability. CVE summarizes:
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.3 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that under certain conditions could have allowed an authenticated user to cause a denial of service due to improper handling of webhook response data.
The weakness was shared by Sim4N6. The advisory is available at hackerone.com. This vulnerability was named CVE-2025-12576 since 10/31/2025. The exploitation appears to be easy. The attack can be initiated remotely. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.
Upgrading to version 18.7.6, 18.8.6 or 18.9.2 eliminates this vulnerability. The upgrade is hosted for download at about.gitlab.com.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://gitlab.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (GitLab): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Community Edition/Enterprise Edition 18.7.6/18.8.6/18.9.2
Timeline
10/31/2025 CVE reserved03/11/2026 Advisory disclosed
03/11/2026 VulDB entry created
03/14/2026 VulDB entry last update
Sources
Vendor: gitlab.comAdvisory: hackerone.com
Researcher: Sim4N6
Status: Confirmed
CVE: CVE-2025-12576 (🔒)
GCVE (CVE): GCVE-0-2025-12576
GCVE (VulDB): GCVE-100-350434
Entry
Created: 03/11/2026 17:31Updated: 03/14/2026 07:36
Changes: 03/11/2026 17:31 (66), 03/14/2026 07:36 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.