GitLabApplication
CVE-2025-12571
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 17.10 before 18.4.5, 18.5 before 18.5.3, and 18.6 before 18.6.1 that could have allowed an unauthenticated user to cause a Denial of Service condition by sending specifically crafted requests containing malicious 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 versions prior to 18.4.5, 18.5.3, and 18.6.1 contain a vulnerability that allows unauthenticated attackers to cause a Denial of Service by sending specifically crafted HTTP requests containing malicious JSON payloads. The issue is network-exploitable and requires no authentication.
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
>= 17.10.0, < 18.4.5>= 18.5.0, < 18.5.3= 18.6.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 command `sudo gitlab-rake gitlab:env:info` and locate the GitLab version line, or check the GitLab admin dashboard under Help > Version, or use package manager commands `dpkg -l | grep gitlab` (Debian) or `rpm -q gitlab-ce` (RHEL/CentOS)Affected if The displayed version falls within any of these ranges: >= 17.10.0 and < 18.4.5, or >= 18.5.0 and < 18.5.3, or exactly 18.6.0
-
Confirm GitLab editionCheck if running Community Edition (CE) or Enterprise Edition (EE) using `sudo gitlab-rake gitlab:env:info` or by viewing the admin panel footer which displays CE or EEAffected if Either edition is present and the version matches the affected ranges from step 1
-
Verify HTTP network exposureConfirm that GitLab web interface is accessible over HTTP/HTTPS from network locations. This is the default configuration and the vulnerability is exploitable via specifically crafted HTTP requests containing malicious JSON payloads sent to any GitLab endpointAffected if GitLab is network-accessible and version is within the affected ranges; the vulnerability requires no authentication and is exploitable remotely
You are affected if your GitLab installation version is 17.10.0 through 18.4.4, 18.5.0 through 18.5.2, or exactly 18.6.0, and the service is accessible over the network.
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.4.518.5.3
Upgrade GitLab to version 18.4.5, 18.5.3, 18.6.1 or later. For production environments, schedule maintenance window, backup data, and follow GitLab upgrade documentation.
Upgrade to GitLab 18.4.5, 18.5.3, or 18.6.1 (whichever is the next available release in your current branch)
- Back up your GitLab instance data and configuration before proceeding
- Stop GitLab services to prevent data inconsistency during upgrade
- Update GitLab to version 18.4.5 (if currently on 17.10-18.4.x), 18.5.3 (if currently on 18.5.x), or 18.6.1 (if currently on 18.6.0) using your package manager or source upgrade method
- Reconfigure GitLab with 'gitlab-ctl reconfigure' if using Omnibus package
- Restart GitLab services
- Verify the upgrade was successful and GitLab is responding to requests
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-12571 — 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-12571 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