dbcve.org
GitLabApplication

CVE-2025-10497

HIGH · 7.5 CVSS v3.1 Published 2025-10-27
Fix available
A fix is available. Upgrade to 18.3.5 / 18.4.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
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.10 before 18.3.5, 18.4 before 18.4.3, and 18.5 before 18.5.1 that could have allowed an unauthenticated attacker to cause a denial of service condition by sending specially crafted payloads.

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 versions prior to 18.3.5, 18.4.3, and 18.5.1 allows unauthenticated attackers to send specially crafted payloads that can cause the service to become unavailable. The vulnerability requires no authentication, making it easily exploitable.

MitigationUpgrade GitLab to version 18.3.5, 18.4.3, 18.5.1 or later to apply the patch. Consider implementing rate limiting or web application firewall rules as a temporary mitigation if immediate upgrade is not feasible.

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:>= 17.10.0, < 18.3.5>= 18.4.0, < 18.4.3= 18.5.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. Check GitLab version via web interface
    Log into the GitLab admin panel or visit the help page (typically at /help) and locate the version number displayed.
    Affected if The displayed version falls within >= 17.10.0 and < 18.3.5, or >= 18.4.0 and < 18.4.3, or equals 18.5.0.
  2. Check GitLab version via API
    Send an unauthenticated GET request to the API endpoint: curl -s https://your-gitlab-instance/api/v4/version
    Affected if The version field in the JSON response falls within the affected ranges.
  3. Check GitLab version via command line
    Run 'gitlab-rake gitlab:env:info' on the GitLab server, or check /opt/gitlab/embedded/service/gitlab-rails/VERSION file.
    Affected if The displayed version falls within the affected ranges.
  4. Verify GitLab is reachable
    Confirm the GitLab instance is accessible over HTTP/HTTPS, as the vulnerability is exploitable via network requests.
    Affected if The instance is online and accepting connections - unauthenticated attackers can exploit it if version is affected.

A GitLab instance is affected if its installed version is 17.10.0 through 18.3.4, 18.4.0 through 18.4.2, or exactly 18.5.0, and the service is accessible over the network.

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.3.5 / 18.4.3 or later
Fixed in 18.3.518.4.3
Interim mitigation

Upgrade GitLab to version 18.3.5, 18.4.3, 18.5.1 or later to apply the patch. Consider implementing rate limiting or web application firewall rules as a temporary mitigation if immediate upgrade is not feasible.

Recommended fix High confidence

18.3.5, 18.4.3, or 18.5.1 (depending on your current major version)

  1. Identify the current GitLab installation version using 'gitlab-rake gitlab:env:info' or the Admin Area dashboard
  2. Determine the appropriate upgrade path based on current version - aim for the earliest fixed release that accommodates your version
  3. For GitLab installations running 17.10.x: upgrade to 18.3.5 or later
  4. For GitLab installations running 18.4.x: upgrade to 18.4.3 or later
  5. For GitLab installations running 18.5.0: upgrade to 18.5.1 or later
  6. Follow the official GitLab upgrade documentation for your deployment method (Omnibus, source, or Helm chart)
  7. Create a backup before upgrading using 'gitlab-backup-create'
  8. Perform the upgrade and verify services are running properly
Caveat Review GitLab release notes for breaking changes between your current and target version, especially when crossing major version boundaries

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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