dbcve.org
GitLabApplication

CVE-2025-2934

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-09
Fix available
A fix is available. Upgrade to 18.2.8 / 18.3.4 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 5.2 prior to 18.2.8, 18.3 prior to 18.3.4, and 18.4 prior to 18.4.2 that could have allowed an authenticated attacker to create a denial of service condition by configuring malicious webhook endpoints that send crafted HTTP responses.

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 attacker can configure malicious webhook endpoints in GitLab that send crafted HTTP responses, causing a denial of service condition by exhausting server resources or triggering processing failures.

MitigationUpdate GitLab to version 18.2.8, 18.3.4, 18.4.2 or later to patch the vulnerability. Review and restrict webhook configuration permissions until patched.

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:>= 5.2.0, < 18.2.8>= 18.3.0, < 18.3.4>= 18.4.0, < 18.4.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. Determine installed GitLab version
    Run command: sudo gitlab-rake gitlab:env:info or check /opt/gitlab/version or check the GitLab admin panel under Admin Area > Overview > Dashboard > GitLab version
    Affected if The installed version falls within < 18.2.8, >= 18.3.0 and < 18.3.4, or >= 18.4.0 and < 18.4.2 (note: versions >= 5.2.0 are affected but older branches may have different version numbering)
  2. Verify webhook feature is enabled
    Check GitLab configuration file /etc/gitlab/gitlab.rb for the setting 'gitlab_rails['webhooks'] = true' or verify through Admin Area > System Settings > Web hooks is not disabled
    Affected if Webhooks are enabled in the GitLab instance (the vulnerability requires the webhook feature to be accessible)
  3. Identify users with webhook configuration permissions
    Navigate to Admin Area > Users and review roles. Users with Maintainer, Developer, or Owner roles on projects can create webhooks. Also check Admin Area > Groups for group-level webhook permissions
    Affected if There are multiple users with permissions to configure webhooks, increasing the attack surface
  4. Review existing webhook configurations for suspicious endpoints
    Use GitLab API: GET /api/v4/projects/:id/hooks or check project Settings > Webhooks in the UI. Look for webhooks with unusual or external URLs, particularly those that may return large payloads or cause timeouts
    Affected if Webhooks exist with external endpoints that are not recognized or that have patterns associated with resource exhaustion (very long timeouts, large response sizes configured)
  5. Check for webhook-related audit events
    Review Admin Area > Audit Events for webhook creation/modification. Filter by event type 'webhook' or 'hook' to identify recent changes
    Affected if There are audit logs showing rapid webhook creation or modification by users, which may indicate exploitation attempts

An instance is affected if it runs a GitLab version in the affected ranges AND has the webhook feature enabled, allowing authenticated users to create webhook configurations that could exhaust server resources.

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.2.8 / 18.3.4 / 18.4.2 or later
Fixed in 18.2.818.3.418.4.2
Interim mitigation

Update GitLab to version 18.2.8, 18.3.4, 18.4.2 or later to patch the vulnerability. Review and restrict webhook configuration permissions until patched.

Recommended fix High confidence

18.2.8, 18.3.4, or 18.4.2 (depending on your current branch; recommended: 18.4.2 for latest)

  1. 1. Identify your current GitLab version by checking the GitLab administration panel or running `gitlab-rake gitlab:env:info`
  2. 2. Based on your current version, determine the appropriate upgrade path:
  3. - If running 18.2.x (before 18.2.8): Upgrade to 18.2.8
  4. - If running 18.3.x (before 18.3.4): Upgrade to 18.3.4
  5. - If running 18.4.x (before 18.4.2): Upgrade to 18.4.2
  6. - If running earlier versions (5.2.0 through 18.1.x): Plan an upgrade to 18.4.2 via an intermediate supported version
  7. 3. Before upgrading, review the GitLab upgrade notes for any required pre-upgrade steps
  8. 4. Perform the upgrade following GitLab's standard upgrade documentation for your deployment method (Omnibus, source, etc.)
Caveat Point releases within the same major.minor version typically do not include breaking changes, but review release notes for any deprecation notices

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

Fix this in GitLab Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2934 — 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-2934 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