dbcve.org
GitLabApplication

CVE-2025-1478

HIGH · 7.5 CVSS v3.1 Published 2025-06-12
Fix available
A fix is available. Upgrade to 17.10.7 / 17.11.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
An issue has been discovered in GitLab CE/EE affecting all versions from 8.13 before 17.10.7, 17.11 before 17.11.3, and 18.0 before 18.0.1. A lack of input validation in Board Names could be used to trigger a denial of service.

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 · moderate confidence

A denial of service vulnerability in GitLab CE/EE stems from insufficient input validation on Board Names. Attackers can exploit this to cause service disruption by submitting specially crafted board names. The issue affects all versions from 8.13 through the vulnerable ranges prior to 17.10.7, 17.11.3, and 18.0.1.

MitigationUpdate GitLab to version 17.10.7, 17.11.3, 18.0.1 or later to patch this vulnerability. As a compensating control, restrict board creation permissions to trusted users until the update is applied.

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:>= 8.13.0, < 17.10.7>= 17.11.0, < 17.11.3= 18.0.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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 Help > Version to determine the exact version number
    Affected if The installed version is >= 8.13.0 and < 17.10.7, OR >= 17.11.0 and < 17.11.3, OR exactly 18.0.0
  2. Verify Boards feature is accessible
    Check if the Boards functionality is enabled for any project or group. Navigate to a project > Boards or check under Admin Area > Settings > Boards to see if the feature is active
    Affected if Boards are enabled and accessible to users who can create or modify board names
  3. Review audit logs for board creation
    Query the GitLab audit logs for events involving board creation or modification. Use Admin Area > Audit Events and filter by event type related to Boards
    Affected if Any board creation events exist in the audit log, indicating the feature has been used
  4. Check for board-related errors in logs
    Examine GitLab production logs (typically in /var/log/gitlab/gitlab-rails/production.log) for errors related to boards that may indicate exploitation attempts
    Affected if Repeated errors or exceptions related to board name processing appear in logs

You are affected if your GitLab version falls within the vulnerable ranges AND the Boards feature is enabled and accessible to 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 17.10.7 / 17.11.3 or later
Fixed in 17.10.717.11.3
Interim mitigation

Update GitLab to version 17.10.7, 17.11.3, 18.0.1 or later to patch this vulnerability. As a compensating control, restrict board creation permissions to trusted users until the update is applied.

Recommended fix High confidence

17.10.7, 17.11.3, or 18.0.1 depending on current branch (17.10.x, 17.11.x, or 18.0.x)

  1. 1. Identify current GitLab version by checking the GitLab administration area or running `gitlab-rake gitlab:env:info`
  2. 2. Based on current version, determine the appropriate upgrade target: for versions 8.13.0 through 17.10.x, upgrade to 17.10.7; for versions 17.11.0 through 17.11.x, upgrade to 17.11.3; for version 18.0.0, upgrade to 18.0.1
  3. 3. Back up the GitLab database and repositories before upgrading
  4. 4. Follow the official GitLab upgrade documentation for your installation method (Omnibus or source)
  5. 5. Run `gitlab-rake gitlab:check` after upgrade to verify integrity
  6. 6. Test board functionality to confirm the DoS vulnerability is remediated
Caveat Review GitLab release notes for breaking changes between your current version and target version before upgrading

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-1478 — 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-1478 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