High

GitLab EE webhook deletion audit log credential retention

IdentifiersCVE-2024-7586CWE-532· Insertion of Sensitive Information…

CVE-2024-7586 is an information exposure vulnerability in GitLab Enterprise Edition. In affected versions, deleting a webhook could result in the associated audit log entry preserving webhook authentication credentials. The issue affects GitLab EE versions starting from 17.0 before 17.0.6, starting from 17.1 before 17.1.4, and starting from 17.2 before 17.2.2. The flaw is a sensitive-data exposure condition in audit logging, where credential material that should not be retained in logs remains recorded during the webhook deletion event.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in exposure of webhook authentication credentials to parties able to access the relevant audit logs. This can compromise the confidentiality of secrets associated with webhook integrations and may enable unauthorized use of those credentials against connected services or workflows, depending on how the webhook authentication was configured and what downstream privileges the credentials carry.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to GitLab audit logs and administrative interfaces to minimize exposure of retained credentials. Avoid unnecessary webhook deletion operations until the instance is upgraded, and proactively rotate webhook authentication credentials where exposure is suspected. Additional compensating controls may include tighter monitoring of audit-log access and review of integrations that rely on webhook secrets.

Remediation

Patch, then assume compromise.

Upgrade GitLab Enterprise Edition to a fixed release: 17.0.6, 17.1.4, 17.2.2, or a later patched version. Review audit logs generated from webhook deletion events in affected deployments to determine whether authentication credentials were retained, and rotate any exposed webhook secrets or related credentials. Limit access to audit logs to only authorized administrators and security personnel.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

GitLabGitlabapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

3 SOURCESView more in app

gitlab releasesNews

Aug 7, 2024

GitLab Patch Release: 17.2.2, 17.1.4, 17.0.6 | GitLab Docs

A GitLab EE vulnerability where webhook deletion audit logs could preserve authentication credentials.

gitlab releasesNews

Mar 18, 2026

GitLab Patch Release: 17.2.2, 17.1.4, 17.0.6 | GitLab

Sensitive information exposure in GitLab EE where webhook deletion audit logs could retain authentication credentials.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1