GitLabApplication
CVE-2025-4225
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 · uneditedAn issue has been discovered in GitLab CE/EE affecting all versions from 14.1 before 18.1.5, 18.2 before 18.2.5, and 18.3 before 18.3.1 that that under certain conditions could have allowed an unauthenticated attacker to cause a denial-of-service condition affecting all users by sending specially crafted GraphQL requests.
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 confidenceGitLab CE/EE contains a denial-of-service vulnerability in its GraphQL API endpoint. An unauthenticated attacker can send specially crafted GraphQL requests that cause the service to become unavailable, affecting all users of the affected instance.
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
>= 14.1.0, < 18.1.5>= 18.2.0, < 18.2.5= 18.3.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed GitLab versionRun `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under /help for the version numberAffected if The version shown is >= 14.1.0 and < 18.1.5, OR >= 18.2.0 and < 18.2.5, OR exactly 18.3.0
-
Confirm GraphQL endpoint is accessibleAttempt to access the GraphQL endpoint at /api/graphql (or /-/graphql for older versions) on the GitLab instance without authenticationAffected if The endpoint responds to unauthenticated requests (returns GraphQL schema or error rather than authentication redirect)
-
Check if instance has public network accessVerify whether the GitLab instance is directly exposed to the internet or accessible from untrusted networksAffected if The instance is reachable from untrusted networks and the GraphQL endpoint does not require authentication
The environment is affected if the installed GitLab version falls within the vulnerable ranges AND the GraphQL endpoint is accessible to unauthenticated users, as this allows remote attackers to trigger the denial-of-service condition.
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.1.518.2.5
Upgrade GitLab to version 18.1.5, 18.2.5, 18.3.1 or later. Alternatively, if immediate upgrade is not feasible, consider restricting or disabling the GraphQL endpoint at the load balancer/reverse proxy level until the patch can be applied.
Upgrade to GitLab 18.1.5, 18.2.5, or 18.3.1 (or later)
- 1. Back up your GitLab instance database and configuration files.
- 2. Schedule a maintenance window as the upgrade will require downtime.
- 3. For GitLab installations using the official omnibus package, run: sudo apt-get update && sudo apt-get install gitlab-ce (or gitlab-ee for Enterprise Edition).
- 4. For installations using source, follow the upgrade path in GitLab's documentation for your specific version.
- 5. After upgrade, verify GitLab is running: sudo gitlab-rake gitlab:env:info
- 6. Test GraphQL endpoint functionality to confirm the service is operational.
- 7. Monitor system resources to verify the DoS condition is remediated.
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 / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4225 — 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-4225 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