dbcve.org
GitLabApplication

CVE-2025-12576

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 18.7.6 / 18.8.6 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.3 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that under certain conditions could have allowed an authenticated user to cause a denial of service due to improper handling of webhook response data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An authenticated user can cause a denial of service in GitLab CE/EE by sending specially crafted webhook response data that is improperly handled by the application, leading to service disruption.

MitigationUpgrade GitLab to version 18.7.6, 18.8.6, or 18.9.2 or later. No workarounds are available; webhooks are a legitimate feature and cannot be disabled to mitigate this issue.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 9.3.0, < 18.7.6>= 18.8.0, < 18.8.6>= 18.9.0, < 18.9.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify GitLab installation version
    Run command: `gitlab-rake gitlab:env:info` or check `/opt/gitlab/version` or use `gitlab --version`
    Affected if Version falls within >= 9.3.0 and < 18.7.6, OR >= 18.8.0 and < 18.8.6, OR >= 18.9.0 and < 18.9.2
  2. Confirm webhooks are accessible
    Navigate to GitLab admin area or project settings and verify webhooks functionality exists or check webhook configuration files in `/opt/gitlab/` directory
    Affected if Webhooks feature is present in the GitLab instance (this is a default feature and cannot be disabled)
  3. Check for webhook usage logs
    Review GitLab production logs for webhook-related entries: `sudo gitlab-ctl tail production.log | grep webhook`
    Affected if Webhooks have been configured and triggered in the environment, creating potential attack surface

Environment is affected if GitLab version is 9.3.0 or higher but below 18.7.6, OR below 18.8.6, OR below 18.9.2, and webhooks feature is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 18.7.6 / 18.8.6 / 18.9.2 or later
Fixed in 18.7.618.8.618.9.2
Interim mitigation

Upgrade GitLab to version 18.7.6, 18.8.6, or 18.9.2 or later. No workarounds are available; webhooks are a legitimate feature and cannot be disabled to mitigate this issue.

Recommended fix High confidence

Upgrade to GitLab 18.7.6, 18.8.6, or 18.9.2 (or later in respective branches)

  1. Identify the currently installed GitLab version by running `gitlab-rake gitlab:env:info` or checking the GitLab admin area
  2. Determine which upgrade path applies based on your current version: if >= 9.3.0 and < 18.7.6, upgrade to 18.7.6+; if >= 18.8.0 and < 18.8.6, upgrade to 18.8.6+; if >= 18.9.0 and < 18.9.2, upgrade to 18.9.2+
  3. Follow the official GitLab upgrade documentation for your installation method (Omnibus or source)
  4. Create a full backup of your GitLab instance before upgrading using `gitlab-backup-create`
  5. Stop GitLab services with `gitlab-ctl stop`
  6. Update GitLab using your package manager (e.g., `apt-get update && apt-get install gitlab-ce` for Omnibus) or by following source upgrade steps
  7. Reconfigure GitLab with `gitlab-ctl reconfigure`
  8. Start GitLab services with `gitlab-ctl start`
Caveat GitLab major version upgrades may include breaking changes; review the CHANGELOG and upgrade guides for your specific version path

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12576 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12576 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data