Credential disclosure via webhook deletion audit logging
Published Jun 20, 2025 · Updated Jun 20, 2025
Sensitive-data logging in GitLab EE allows remote authenticated users with high privileges to expose webhook credentials in deletion audit logs. The webhook-deletion audit path records authentication material in the resulting audit entry instead of removing it before persistence. Reaching the flaw requires high privileges and deleting a webhook, and the reported consequence is limited to disclosure of the retained credential.
Summary
What happened
Sensitive-data logging in GitLab EE allows remote authenticated users with high privileges to expose webhook credentials in deletion audit logs. The webhook-deletion audit path records authentication material in the resulting audit entry instead of removing it before persistence. Reaching the flaw requires high privileges and deleting a webhook, and the reported consequence is limited to disclosure of the retained credential.
The record
- CVE
- CVE-2024-7586
- Published
- Jun 20, 2025
- Updated
- Jun 20, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-532, T1552
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jun 20, 2025CVE publishedPublication date reported by the CVE source.
- Jun 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=17.0 <17.0.6
- Affected versionversion=17.1 <17.1.4
- Affected versionversion=17.2 <17.2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo