GitLab Enterprise Edition up to 18.0.4/18.1.2/18.2.0 Duo Response exposure of sensitive information

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.6$0-$5k0.00

Summaryinfo

A vulnerability was found in GitLab Enterprise Edition up to 18.0.4/18.1.2/18.2.0. It has been rated as problematic. This vulnerability affects unknown code of the component Duo Response Handler. This manipulation causes exposure of sensitive information. This vulnerability is registered as CVE-2025-4976. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability classified as problematic was found in GitLab Enterprise Edition up to 18.0.4/18.1.2/18.2.0. Affected by this vulnerability is an unknown function of the component Duo Response Handler. The manipulation with an unknown input leads to a exposure of sensitive information vulnerability. The CWE definition for the vulnerability is CWE-213. The product's intended functionality exposes information to certain actors in accordance with the developer's security policy, but this information is regarded as sensitive according to the intended security policies of other stakeholders such as the product's administrator, users, or others whose information is being processed. As an impact it is known to affect confidentiality. The summary by CVE is:

An issue has been discovered in GitLab EE affecting all versions from 17.0 before 18.0.5, 18.1 before 18.1.3, and 18.2 before 18.2.1 that, under certain circumstances, could have allowed an attacker to access internal notes in GitLab Duo responses.

The weakness was published by rogerace. The advisory is shared at gitlab.com. This vulnerability is known as CVE-2025-4976 since 05/20/2025. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 242661 (GitLab 17.0 < 18.0.5 / 18.1 < 18.1.3 / 18.2 < 18.2.1 (CVE-2025-4976)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 18.0.5, 18.1.3 or 18.2.1 eliminates this vulnerability.

The vulnerability is also documented in the databases at Tenable (242661), EUVD (EUVD-2025-22481) and CERT Bund (WID-SEC-2025-1627). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

  • Open Source GitLab

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.6
VulDB Meta Temp Score: 4.6

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍

NVD Base Score: 5.3
NVD Vector: 🔒

CNA Base Score: 4.3
CNA Vector (GitLab): 🔒

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Exposure of sensitive information
CWE: CWE-213 / CWE-200 / CWE-284
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 242661
Nessus Name: GitLab 17.0 < 18.0.5 / 18.1 < 18.1.3 / 18.2 < 18.2.1 (CVE-2025-4976)

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Enterprise Edition 18.0.5/18.1.3/18.2.1

Timelineinfo

05/20/2025 CVE reserved
07/24/2025 +65 days Advisory disclosed
07/24/2025 +0 days VulDB entry created
07/28/2025 +4 days VulDB entry last update

Sourcesinfo

Vendor: gitlab.com

Advisory: gitlab.com
Researcher: rogerace
Status: Confirmed

CVE: CVE-2025-4976 (🔒)
GCVE (CVE): GCVE-0-2025-4976
GCVE (VulDB): GCVE-100-317485
EUVD: 🔒
CERT Bund: WID-SEC-2025-1627 - GitLab: Mehrere Schwachstellen

Entryinfo

Created: 07/24/2025 09:16
Updated: 07/28/2025 20:02
Changes: 07/24/2025 09:16 (65), 07/24/2025 15:47 (7), 07/24/2025 16:17 (1), 07/24/2025 20:09 (2), 07/28/2025 20:02 (12)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Might our Artificial Intelligence support you?

Check our Alexa App!