GitLab Community Edition/Enterprise Edition up to 18.7.5/18.8.5/18.9.1 Datadog API escape output
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in GitLab Community Edition and Enterprise Edition up to 18.7.5/18.8.5/18.9.1. This impacts an unknown function of the component Datadog API. The manipulation results in escape output. This vulnerability is identified as CVE-2025-12697. The attack can be executed remotely. There is not any exploit available. You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in GitLab Community Edition and Enterprise Edition up to 18.7.5/18.8.5/18.9.1. Affected is some unknown functionality of the component Datadog API. The manipulation with an unknown input leads to a escape output vulnerability. CWE is classifying the issue as CWE-116. The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved. This is going to have an impact on confidentiality. CVE summarizes:
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.5 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that could have allowed an authenticated user with maintainer-role permissions to reveal Datadog API credentials under certain conditions.
The weakness was released by Shells3C. The advisory is shared for download at hackerone.com. This vulnerability is traded as CVE-2025-12697 since 11/04/2025. The exploitability is told to be difficult. It is possible to launch the attack remotely. The exploitation needs additional levels of successful authentication. There are neither technical details nor an exploit publicly available.
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.
Once again VulDB remains the best source for vulnerability data.
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: 2.9VulDB Meta Temp Score: 2.9
VulDB Base Score: 2.2
VulDB Temp Score: 2.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 4.4
NVD Vector: 🔒
CNA Base Score: 2.2
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: Escape outputCWE: CWE-116 / CWE-74 / CWE-707
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
11/04/2025 CVE reserved03/11/2026 Advisory disclosed
03/11/2026 VulDB entry created
03/18/2026 VulDB entry last update
Sources
Vendor: gitlab.comAdvisory: hackerone.com
Researcher: Shells3C
Status: Confirmed
CVE: CVE-2025-12697 (🔒)
GCVE (CVE): GCVE-0-2025-12697
GCVE (VulDB): GCVE-100-350436
Entry
Created: 03/11/2026 17:32Updated: 03/18/2026 08:46
Changes: 03/11/2026 17:32 (66), 03/14/2026 07:36 (1), 03/18/2026 08:46 (11)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.