CVE-2025-4976 | Exposure of Sensitive Information Due to Incompatible Policies in GitLab

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.

Published: 2025-07-24 Last update: 2025-07-28 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-4976 is rated Low Risk (25.3/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.08%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-4976

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-20 0.01% 0.08% +0.07%
2 2025-07-24 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-4976

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 1.4 [email protected]
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 [email protected]

Weakness enumeration for CVE-2025-4976

OS Trackers for CVE-2025-4976

vendor priority summary link
debian not yet assigned CVE-2025-4976 not yet assigned priority: Debian including 1 source packages (gitlab), 1 status rows across 1 suites (sid): open 1. https://security-tracker.debian.org/tracker/CVE-2025-4976
ubuntu medium CVE-2025-4976 medium priority: Ubuntu including 1 source packages (gitlab), 5 status rows across 5 suites (jammy, noble, plucky, upstream, xenial): DNE 3, ignored 1, needs-triage 1. https://ubuntu.com/security/CVE-2025-4976

Affected software / configurations for CVE-2025-4976

Vendor Product Version Raw CPE
gitlab gitlab >= 17.0.0, < 18.0.5 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
gitlab gitlab >= 18.1.0, < 18.1.3 cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*
gitlab gitlab 18.2 cpe:2.3:a:gitlab:gitlab:18.2:*:*:*:enterprise:*:*:*

References for CVE-2025-4976

cvelogic Threat Intelligence