GitLabApplication
CVE-2025-2615
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 · uneditedGitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.7 before 18.3.6, 18.4 before 18.4.4, and 18.5 before 18.5.2, that could have allowed a blocked user to access sensitive information by establishing GraphQL subscriptions through WebSocket connections.
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 confidenceA vulnerability in GitLab CE/EE allowed blocked users to bypass access controls by establishing GraphQL subscriptions through WebSocket connections, enabling unauthorized access to sensitive information in versions 16.7 through 18.5.1.
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
>= 16.7.0, < 18.3.6>= 18.4.0, < 18.4.4>= 18.5.0, < 18.5.2CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed GitLab versionRun command: sudo gitlab-rake gitlab:env:info or check the GitLab admin area at /help (or /-/profile) which displays the version in the footerAffected if The version displayed falls within any of these ranges: >= 16.7.0 and < 18.3.6, OR >= 18.4.0 and < 18.4.4, OR >= 18.5.0 and < 18.5.2
-
Verify GraphQL API is accessibleMake an HTTP GET request to /api/graphql (e.g., curl https://your-gitlab-instance/api/graphql)Affected if The GraphQL endpoint responds, indicating GraphQL is enabled and reachable over HTTP/HTTPS
-
Check if WebSocket support is enabled for GitLabInspect the GitLab configuration file at /etc/gitlab/gitlab.rb for the setting gitlab_rails['websocket_enabled'] = true, or check the response headers when accessing the web interface for WebSocket upgrade supportAffected if WebSocket connections are allowed (the setting is true or not explicitly disabled) and the GitLab instance is network-accessible to blocked users
-
Confirm blocked user authentication is possibleAttempt to establish a WebSocket connection to /-/graphql-ws or /api/v4/websocket from a blocked test account using a GraphQL clientAffected if The WebSocket connection is successfully established and the blocked user can receive GraphQL subscription events
A user is affected if their GitLab version falls within the vulnerable ranges AND the GraphQL API with WebSocket subscriptions is enabled and accessible to blocked users.
Generated from the published advisory. Verify against your own configuration.
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 · scoped18.3.618.4.418.5.2
Upgrade GitLab to version 18.3.6, 18.4.4, 18.5.2 or later to remediate this vulnerability.
Upgrade to GitLab 18.3.6, 18.4.4, or 18.5.2 (or later respective versions)
- 1. Back up your GitLab instance data and configuration
- 2. Ensure you have a recovery plan in case of upgrade issues
- 3. For self-managed GitLab installations, stop the GitLab services before upgrading
- 4. Upgrade GitLab to version 18.3.6 (or later in 18.3.x), 18.4.4 (or later in 18.4.x), or 18.5.2 (or later in 18.5.x)
- 5. Verify the upgrade was successful by checking the GitLab version in the UI or via CLI: gitlab-rake gitlab:env:info
- 6. Test that blocked users cannot establish GraphQL subscriptions via WebSocket
- 7. Restart GitLab services if they were stopped
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2615 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-2615 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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