dbcve.org
GitLabApplication

CVE-2025-11865

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-15
Fix available
A fix is available. Upgrade to 18.3.6 / 18.4.4 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
An issue has been discovered in GitLab EE affecting all versions from 18.1 before 18.3.6, 18.4 before 18.4.4, and 18.5 before 18.5.2 that, under certain circumstances, could have allowed an attacker to remove Duo flows of another user.

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 confidence

This is an access control vulnerability in GitLab EE where an authenticated attacker could remove Duo AI flows belonging to another user, likely due to improper authorization checks (IDOR) when handling flow deletion requests.

MitigationUpdate GitLab EE to version 18.3.6, 18.4.4, or 18.5.2 or later to receive the security patch.

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
Affected:>= 18.1.0, < 18.3.6>= 18.4.0, < 18.4.4>= 18.5.0, < 18.5.2

CVSS 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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed GitLab EE version
    Run `sudo gitlab-rake gitlab:env:info` or `sudo gitlab-ctl version` to display the installed GitLab version. Alternatively, check the /opt/gitlab/version file or the Admin Area > Settings > General page in the web UI.
    Affected if The version falls within these ranges: >= 18.1.0 and < 18.3.6, OR >= 18.4.0 and < 18.4.4, OR >= 18.5.0 and < 18.5.2
  2. Verify GitLab Duo Enterprise is enabled
    Navigate to Admin Area > GitLab Duo > Duo Enterprise (or check via API: GET /application/settings), or inspect the gitlab.rb config file for duo_features_enabled settings.
    Affected if GitLab Duo Enterprise features are enabled and the version is in the affected range listed above
  3. Review audit logs for unauthorized flow deletions
    Access the audit log via Admin Area > Monitoring > Audit Logs, or query the audit_events table. Search for event_type containing 'flow' and action 'destroy' or 'delete' around Duo-related resources.
    Affected if Audit log entries show flow deletion events initiated by one user targeting another user's flows (check user_id and target_user_id mismatch)
  4. Check for missing Duo AI flows
    Query the ai_agents or similar Duo flow tables in the GitLab database (psql) to list current flows, or have users verify their configured Duo AI workflows are intact via the UI at User Settings > GitLab Duo.
    Affected if Users report missing or deleted Duo AI flows that they did not remove themselves

You are affected if running a GitLab EE version in the vulnerable range (18.1.0 to 18.3.5, 18.4.0 to 18.4.3, or 18.5.0 to 18.5.1) with Duo Enterprise enabled and unauthorized flow deletions are present in audit logs or reported by users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 18.3.6 / 18.4.4 / 18.5.2 or later
Fixed in 18.3.618.4.418.5.2
Interim mitigation

Update GitLab EE to version 18.3.6, 18.4.4, or 18.5.2 or later to receive the security patch.

Recommended fix High confidence

18.5.2 (or 18.3.6 minimum for 18.1-18.3.x range, 18.4.4 for 18.4.x range)

  1. 1. Back up your GitLab instance data before performing any upgrade
  2. 2. Plan for maintenance window as upgrade may require downtime
  3. 3. Upgrade GitLab to version 18.3.6 or later if currently on 18.1.x-18.3.x
  4. 4. Upgrade GitLab to version 18.4.4 or later if currently on 18.4.x
  5. 5. Upgrade GitLab to version 18.5.2 or later if currently on 18.5.x
  6. 6. Verify the upgrade completed successfully
  7. 7. Test that users can only modify their own Duo flows and not other users' flows
Caveat Standard GitLab upgrade risks apply - review GitLab release notes for any configuration or API changes before upgrading

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11865 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11865 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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