dbcve.org
GitLabApplication

CVE-2025-3111

MEDIUM · 6.5 CVSS v3.1 Published 2025-05-22
Fix available
A fix is available. Upgrade to 17.10.7 / 17.11.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
An issue has been discovered in GitLab CE/EE affecting all versions from 10.2 before 17.10.7, 17.11 before 17.11.3, and 18.0 before 18.0.1. A lack of input validation in the Kubernetes integration could allow an authenticated user to cause 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 · high confidence

GitLab CE/EE versions prior to 17.10.7, 17.11.3, and 18.0.1 contain a lack of input validation in the Kubernetes integration feature. An authenticated user can exploit this vulnerability to cause a denial of service condition through malformed or specially crafted input to the Kubernetes integration.

MitigationUpgrade GitLab to version 17.10.7, 17.11.3, 18.0.1 or later. Alternatively, restrict access to the Kubernetes integration feature until the upgrade can be performed.

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:>= 10.2.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
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 `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under Help > Version to find the exact version number
    Affected if Version is 10.2.0 or higher but below 17.10.7, OR 17.11.0-17.11.2, OR exactly 18.0.0
  2. Verify Kubernetes integration is accessible
    Check if the Kubernetes integration feature is enabled in the GitLab admin settings under Kubernetes cluster integrations, or check if any projects have Kubernetes clusters configured
    Affected if Kubernetes integration is enabled or configured for any project accessible to authenticated users
  3. Confirm authenticated user access exists
    Review user authentication settings and verify that non-admin authenticated users can access the GitLab instance and interact with project settings
    Affected if Authenticated users (non-admin) have access to create or modify Kubernetes integrations

You are affected if your GitLab version falls within the vulnerable ranges AND the Kubernetes integration feature is accessible to authenticated users on your instance.

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

Upgrade GitLab to version 17.10.7, 17.11.3, 18.0.1 or later. Alternatively, restrict access to the Kubernetes integration feature until the upgrade can be performed.

Recommended fix High confidence

17.10.7, 17.11.3, or 18.0.1 depending on current version

  1. 1. Back up your GitLab instance data and configuration before upgrading.
  2. 2. For GitLab installations using Omnibus: run 'sudo gitlab-ctl stop' to stop services.
  3. 3. Update to the appropriate fixed version based on your current version:
  4. - If running 10.2.0 to 17.9.x: upgrade to 17.10.7
  5. - If running 17.11.0 to 17.11.2: upgrade to 17.11.3
  6. - If running 18.0.0: upgrade to 18.0.1
  7. 4. For Omnibus installations, update using your package manager (e.g., 'apt-get update && apt-get install gitlab-ce' or 'yum install gitlab-ce').
  8. 5. For source installations, pull the specific tagged release from git and rebuild.
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
  • 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-3111 — 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-3111 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