dbcve.org
GitLabApplication

CVE-2026-3848

MEDIUM · 5.0 CVSS v3.1 Published 2026-03-11
Fix available
A fix is available. Upgrade to 18.7.6 / 18.8.6 or later.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable 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
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 8.11 before 18.7.6, 18.8 before 18.8.6, and 18.9 before 18.9.2 that could have allowed an authenticated user to make unintended internal requests through proxy environments under certain conditions due to improper input validation in import functionality.

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 confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in GitLab's import functionality where improper input validation allows authenticated users to make unintended internal requests through proxy environments. The flaw enables attackers to potentially access internal services or bypass network restrictions.

MitigationUpgrade GitLab to version 18.7.6, 18.8.6, or 18.9.2 or later to remediate this vulnerability.

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:>= 8.11.0, < 18.7.6>= 18.8.0, < 18.8.6>= 18.9.0, < 18.9.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
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/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 version
    Run `sudo gitlab-rake gitlab:version` or check /opt/gitlab/version on the GitLab server
    Affected if The version falls within the affected ranges: < 18.7.6, 18.8.0-18.8.6, or 18.9.0-18.9.2 (note: versions 8.11.0 to 18.6.x are also affected if below 18.7.6)
  2. Verify GitLab import functionality is enabled
    Check if import features are enabled in Admin Area > Settings > General > Import and export settings, or inspect the gitlab.yml configuration file
    Affected if Import sources are enabled and accessible to users
  3. Confirm authenticated user access exists
    Review user accounts and groups that have permission to perform project imports (check Admin Area > Users and project membership settings)
    Affected if There are authenticated users with import/create project permissions who could exploit this flaw
  4. Identify exposed network interfaces
    Review GitLab's configuration in /etc/gitlab/gitlab.rb for `gitlab_workhorse` settings and check if the server can reach internal network resources
    Affected if GitLab has network access to internal services that could be targeted via SSRF

You are affected if your GitLab version is 18.7.6 or lower, or falls between 18.8.0-18.8.6, or 18.9.0-18.9.2 AND the import functionality is enabled for authenticated users on a server with internal network access.

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.7.6 / 18.8.6 / 18.9.2 or later
Fixed in 18.7.618.8.618.9.2
Interim mitigation

Upgrade GitLab to version 18.7.6, 18.8.6, or 18.9.2 or later to remediate this vulnerability.

Recommended fix High confidence

18.7.6, 18.8.6, 18.9.2, or latest stable (18.10.0+)

  1. 1. Backup your GitLab instance data and configuration before proceeding with the upgrade
  2. 2. Identify your current GitLab version by navigating to Admin Area > Dashboard or running `gitlab-rake gitlab:env:info`
  3. 3. If running version 8.11.0 through 18.7.x, upgrade to version 18.7.6 or later
  4. 4. If running version 18.8.x, upgrade to version 18.8.6 or later
  5. 5. If running version 18.9.x, upgrade to version 18.9.2 or later
  6. 6. For best results, upgrade to the latest stable release (18.10.0 or newer) to receive all security patches
  7. 7. After upgrade, verify the GitLab instance is functioning correctly and test the import functionality
Caveat Major GitLab upgrades between multiple version branches may require following the official upgrade path documentation and running necessary database migrations

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
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3848 — 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-2026-3848 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