dbcve.org
GitLabApplication

CVE-2025-13078

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to 18.8.7 / 18.9.3 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 16.10 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 that could have allowed an authenticated user to cause a denial of service due to excessive resource consumption when processing certain webhook configuration inputs.

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 denial of service by sending specially crafted webhook configuration inputs that trigger excessive resource consumption in GitLab CE/EE versions 16.10 through 18.10 (before patched versions). The vulnerability stems from insufficient input validation on webhook configuration processing.

MitigationUpgrade GitLab to versions 18.8.7, 18.9.3, 18.10.1 or later. For environments that cannot immediately upgrade, consider restricting webhook creation/modification permissions to trusted users and implementing rate limiting on webhook endpoints.

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:>= 16.10.0, < 18.8.7>= 18.9.0, < 18.9.3= 18.10.0

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 installed GitLab version
    Run `gitlab-rake gitlab:version` or check the GitLab admin panel under Admin Area > Overview > Dashboard. Alternatively, check the /opt/gitlab/version file if installed via omnibus package.
    Affected if The installed version falls within 16.10.0 to 18.8.6, 18.9.0 to 18.9.2, or equals 18.10.0.
  2. Verify webhook functionality is accessible
    Navigate to a project or group settings and check if Webhooks are listed under Settings > Webhooks, or query the API endpoint `/projects/:id/hooks` using a valid API token.
    Affected if Webhook feature is enabled and accessible to authenticated users in the environment.
  3. Confirm user permissions allow webhook creation
    Review the GitLab administration settings under Admin Area > Settings > Webhooks, or check the default project/group member roles to see if non-admin users have permission to create or modify webhooks.
    Affected if Authenticated users with webhook creation or modification permissions exist in the system.

You are affected if your GitLab version is within the vulnerable range AND webhook creation/modification is accessible to authenticated users in your environment.

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.8.7 / 18.9.3 or later
Fixed in 18.8.718.9.3
Interim mitigation

Upgrade GitLab to versions 18.8.7, 18.9.3, 18.10.1 or later. For environments that cannot immediately upgrade, consider restricting webhook creation/modification permissions to trusted users and implementing rate limiting on webhook endpoints.

Recommended fix High confidence

GitLab 18.10.1 or later (latest stable 18.x release)

  1. 1. Back up your GitLab instance data before starting the upgrade process
  2. 2. Review the GitLab upgrade documentation for your installation method (package, source, etc.)
  3. 3. Plan for downtime as GitLab upgrades typically require service interruption
  4. 4. Upgrade to GitLab version 18.10.1 or later (the latest stable 18.x release recommended)
  5. 5. After upgrade, verify GitLab services are running properly
  6. 6. Test webhook functionality to confirm the fix is working
Caveat Standard GitLab upgrade considerations apply - review the release notes for any between-version migrations or breaking changes

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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