CVE-2025-0194

Public Exploit
Insertion of Sensitive Information into Externally-Accessible File or Directory in GitLab

Description

An issue was discovered in GitLab CE/EE affecting all versions starting from 17.4 prior to 17.5.5, starting from 17.6 prior to 17.6.3, and starting from 17.7 prior to 17.7.1. Under certain conditions, access tokens may have been logged when API requests were made in a specific manner.

Remediation

Solution:

  • Upgrade to version 17.5.5, 17.6.3 or 17.7.1 or above

Category

6.5
CVSS
Severity: Medium
CVSS 3.1 •
EPSS 0.02%
Vendor Advisory gitlab.com
Affected: GitLab GitLab
Published at:
Updated at:

References

Link Tags
https://gitlab.com/gitlab-org/gitlab/-/issues/489459 exploit issue tracking vendor advisory permissions required
https://about.gitlab.com/releases/2025/01/08/patch-release-gitlab-17-7-1-released/#possible-access-token-exposure-in-gitlab-logs release notes

Frequently Asked Questions

What is the severity of CVE-2025-0194?
CVE-2025-0194 has been scored as a medium severity vulnerability.
How to fix CVE-2025-0194?
To fix CVE-2025-0194: Upgrade to version 17.5.5, 17.6.3 or 17.7.1 or above
Is CVE-2025-0194 being actively exploited in the wild?
It is possible that CVE-2025-0194 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2025-0194?
CVE-2025-0194 affects GitLab GitLab.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.