GitLabApplication
CVE-2025-11702
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 EE affecting all versions from 17.1 before 18.3.5, 18.4 before 18.4.3, and 18.5 before 18.5.1 that could have allowed an authenticated attacker with specific permissions to hijack project runners from other projects.
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 · moderate confidenceGitLab EE versions 17.1 through 18.5 before specific patch releases contained an authorization flaw that allowed an authenticated attacker with certain project permissions to hijack CI/CD runners belonging to other projects, enabling unauthorized execution of pipelines under compromised runner contexts.
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.1.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 GitLab EE versionRun `sudo gitlab-rake gitlab:version` or check the GitLab admin area under Help > Version to see the exact installed versionAffected if The installed version falls within >= 17.1.0 and < 18.3.5, OR >= 18.4.0 and < 18.4.3, OR equals 18.5.0
-
Verify CI/CD runners existNavigate to Settings > CI/CD > Runners in the GitLab UI or query the API endpoint `/api/v4/runners` with admin credentials to list registered runnersAffected if Runners are registered and active in the GitLab instance
-
Check runner assignment permissionsReview project-level runner settings under Settings > CI/CD > Runners for each project; verify if projects share runners or have runner permissions that allow cross-project assignmentAffected if Runners are shared across multiple projects or non-owner users can modify runner assignments
You are affected if your GitLab EE version is one of the vulnerable releases AND you have CI/CD runners configured that could be reassigned by users with project access rights.
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 EE to versions 18.3.5, 18.4.3, 18.5.1 or later to remediate the runner hijacking vulnerability. Review runner configurations and audit runner assignment permissions post-upgrade.
GitLab 18.5.1 (or latest 18.x stable)
- 1. Backup your GitLab instance data and configuration
- 2. Schedule a maintenance window as upgrade may require downtime
- 3. For GitLab 17.1.x through 18.3.4: Upgrade to GitLab 18.3.5 or later
- 4. For GitLab 18.4.0 through 18.4.2: Upgrade to GitLab 18.4.3 or later
- 5. For GitLab 18.5.0: Upgrade to GitLab 18.5.1 or later
- 6. After upgrade, verify runner configuration in Admin Area > Runners to confirm no unauthorized changes
- 7. Review project runner assignments in affected projects to ensure integrity
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11702 — 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-11702 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