GitLabApplication
CVE-2025-7734
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.2 before 18.0.6, 18.1 before 18.1.4 and 18.2 before 18.2.2 that, under certain conditions, could have allowed a successful attacker to execute actions on behalf of users by injecting malicious content.
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 an injection vulnerability in versions 14.2 through 18.0.5, 18.1.0-18.1.3, and 18.2.0-18.2.1 that allows attackers to inject malicious content and execute actions on behalf of authenticated users under certain conditions.
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.2.0, < 18.0.6>= 18.1.0, < 18.1.4>= 18.2.0, < 18.2.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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 your GitLab installation versionRun `gitlab-rake gitlab:env:info` or check `/opt/gitlab/version` for omnibus installations, or `cat VERSION` in the source directory for source installationsAffected if The version number returned falls within these ranges: >= 14.2.0 and < 18.0.6; >= 18.1.0 and < 18.1.4; >= 18.2.0 and < 18.2.2
-
Verify external user authentication is enabledCheck the GitLab admin area under Settings > General > Visibility and access controls, or inspect `gitlab.yml` for `gitlab.default_can_create_group` and user sign-up settingsAffected if External or non-admin user registration or sign-in is permitted, allowing authenticated users to access the instance
-
Identify if the instance has authenticated users beyond administratorsRun `gitlab-rake gitlab:users:list` or check the admin dashboard Users page to confirm the presence of non-admin user accountsAffected if There are authenticated non-admin users present in the GitLab instance
Your environment is affected if the installed GitLab version falls within the affected ranges AND authenticated non-admin users can access the system, since the injection vulnerability requires authenticated user context to be exploitable.
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.0.618.1.418.2.2
Upgrade GitLab to version 18.0.6, 18.1.4, or 18.2.2 or later to patch the vulnerability.
18.2.2 (or 18.1.4 or 18.0.6 depending on your current branch)
- Identify your current GitLab version by running `gitlab-rake gitlab:env:info` or checking the GitLab admin area
- Determine which upgrade path applies based on your current version: if running 18.0.x, upgrade to 18.0.6; if running 18.1.x, upgrade to 18.1.4; if running 18.2.x, upgrade to 18.2.2
- Before upgrading, back up your GitLab data following the official backup documentation at docs.gitlab.com/ee/raketasks/backup_restore.html
- Upgrade GitLab to the appropriate fixed version using your installation method (omnibus, source, or package)
- After upgrade, verify the new version is running with `gitlab-rake gitlab:env:info`
- Confirm the vulnerability is resolved by checking that the specific injected content no longer executes
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
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-7734 — 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-7734 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