CVE-2025-2469: Debug Messages Revealing Unnecessary Information in GitLab
First published: Thu Apr 10 2025(Updated: )
An issue has been discovered in GitLab CE/EE affecting all versions from 17.9 before 17.9.6, and 17.10 before 17.10.4. The runtime profiling data of a specific service was accessible to unauthenticated users.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >17.9<17.9.6 | |
| GitLab Enterprise Edition | >17.10<17.10.4 |
Remedy
Upgrade to version 17.10.4, 17.9.6
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-2469?
The severity of CVE-2025-2469 is considered to be moderate due to the exposure of sensitive runtime profiling data.
How do I fix CVE-2025-2469?
To fix CVE-2025-2469, upgrade GitLab CE to version 17.9.6 or higher and GitLab EE to version 17.10.4 or higher.
Who is affected by CVE-2025-2469?
CVE-2025-2469 affects all versions of GitLab CE from 17.9 before 17.9.6 and GitLab EE from 17.10 before 17.10.4.
What type of data was exposed in CVE-2025-2469?
CVE-2025-2469 exposed the runtime profiling data of a specific service to unauthenticated users.
Is CVE-2025-2469 exploitable remotely?
Yes, CVE-2025-2469 is remotely exploitable as it allows unauthenticated users access to sensitive data.
- collector/mitre-cve
- source/MITRE
- agent/remedy
- agent/references
- agent/title
- agent/weakness
- agent/description
- agent/first-publish-date
- agent/type
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/severity
- agent/source
- agent/author
- agent/tags
- agent/event
- vendor/gitlab
- canonical/gitlab
- canonical/gitlab enterprise edition