GitLabApplication
CVE-2025-11447
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 11.0 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 GraphQL requests with crafted JSON 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 · high confidenceGitLab CE/EE contains a denial of service vulnerability in its GraphQL API endpoint. An unauthenticated attacker can send specially crafted JSON payloads in GraphQL requests that cause the application to become unresponsive or crash, affecting availability.
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
>= 11.0.0, < 18.3.5>= 18.4.0, < 18.4.3= 18.5.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.
-
Check GitLab versionRun `gitlab-rake gitlab:env:info` or check the /opt/gitlab/version file to determine the installed GitLab version.Affected if The version falls within any of these ranges: >= 11.0.0 and < 18.3.5, >= 18.4.0 and < 18.4.3, or equals 18.5.0.
-
Verify GraphQL API is accessibleConfirm that the GraphQL endpoint (typically at /api/graphql) is exposed and accessible to unauthenticated users. This can be tested by sending a GraphQL query request without providing authentication credentials.Affected if The GraphQL endpoint responds to unauthenticated requests.
-
Confirm availability impactObserve application responsiveness. Attempt to send a crafted JSON payload to the GraphQL endpoint and monitor for service degradation or unresponsiveness.Affected if The application becomes unresponsive or crashes when processing specially crafted GraphQL JSON payloads from unauthenticated sources.
A user is affected if their GitLab version is 11.0.0 through 18.3.4, 18.4.0 through 18.4.2, or 18.5.0 AND the GraphQL API endpoint is accessible to unauthenticated 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.518.4.3
Upgrade GitLab to version 18.3.5, 18.4.3, 18.5.1 or later. If immediate patching is not possible, consider restricting or rate-limiting unauthenticated GraphQL API access at the network level as a temporary mitigation.
GitLab 18.5.1 or later (18.3.5 for 11.0-18.3.x, 18.4.3 for 18.4.x, 18.5.1 for 18.5.0)
- Back up your GitLab instance data and configuration before upgrading
- Ensure your system meets the requirements for the target GitLab version
- Upgrade GitLab to version 18.3.5 (if currently on 11.0.0 to 18.3.4), 18.4.3 (if currently on 18.4.0 to 18.4.2), or 18.5.1 (if currently on 18.5.0)
- After upgrading, verify that GitLab services are running correctly
- Test GraphQL functionality to confirm the vulnerability is remediated
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
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11447 — 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-11447 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