dbcve.org
GitLabApplication

CVE-2022-3726

CRITICAL · 9.0 CVSS v3.1 Published 2022-11-10
Fix available
A fix is available. Upgrade to 15.3.5 / 15.4.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable

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
Lack of sand-boxing of OpenAPI documents in GitLab CE/EE affecting all versions from 12.6 prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 allows an attacker to trick a user to click on the Swagger OpenAPI viewer and issue HTTP requests that affect the victim's account.

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

A cross-site request forgery (CSRF) or SSRF vulnerability in GitLab's Swagger/OpenAPI document viewer allows attackers to trick authenticated users into viewing malicious OpenAPI documents that trigger unauthorized HTTP requests to internal services or the GitLab API, performing actions as the victim user.

MitigationUpgrade GitLab to version 15.3.5, 15.4.4, or 15.5.2 or later. Until patched, warn users not to open untrusted OpenAPI/Swagger documents in the GitLab UI.

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:>= 12.6.0, < 15.3.5>= 15.4.0, < 15.4.4>= 15.5.0, < 15.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
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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

  1. Determine the installed GitLab version
    Run `gitlab-rake gitlab:env:info` or check the GitLab admin dashboard under 'Admin Area > Metrics and Monitoring > Version' to find the exact version number
    Affected if The version falls within any of these ranges: >= 12.6.0 and < 15.3.5, OR >= 15.4.0 and < 15.4.4, OR >= 15.5.0 and < 15.5.2
  2. Verify the OpenAPI viewer feature is accessible
    Check if regular (non-admin) users can access repositories or projects containing OpenAPI (.yaml or .json) files. Attempt to view an OpenAPI file in the GitLab UI by navigating to a project and clicking on an uploaded .yaml or .json file
    Affected if The OpenAPI document viewer loads and renders the file in the browser for authenticated users
  3. Check for external network access from GitLab server
    Review GitLab server network configuration to determine if outbound HTTP/HTTPS connections to internal services or the GitLab API itself are possible from the server
    Affected if The GitLab server can make HTTP requests to internal services or localhost, allowing a malicious OpenAPI document to trigger SSRF
  4. Confirm authenticated user access to file uploads
    Verify that users with at least Developer or Reporter role can upload or create files in projects. Check project settings under 'Settings > Repository' for 'Push rules' or review user role permissions
    Affected if Users can push or create files containing OpenAPI specifications that would be rendered by the viewer

You are affected if your GitLab version is within the affected ranges AND the OpenAPI document viewer feature is accessible to authenticated users who can upload or view OpenAPI files.

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 15.3.5 / 15.4.4 / 15.5.2 or later
Fixed in 15.3.515.4.415.5.2
Interim mitigation

Upgrade GitLab to version 15.3.5, 15.4.4, or 15.5.2 or later. Until patched, warn users not to open untrusted OpenAPI/Swagger documents in the GitLab UI.

Recommended fix High confidence

Upgrade to GitLab 15.5.2, 15.4.4, or 15.3.5 (or later) depending on your release line

  1. 1. Back up your GitLab instance data and configuration before starting the upgrade.
  2. 2. Review GitLab release notes for the target version to understand any required pre-upgrade steps.
  3. 3. For installations using Omnibus packages: Run 'sudo apt-get update' and 'sudo apt-get install gitlab-ce' (or 'gitlab-ee') to upgrade to the latest patched version.
  4. 4. For installations using source: Clone the specific tagged release (e.g., 'v15.5.2') and follow the upgrade documentation.
  5. 5. After upgrade, verify GitLab is running: check the version with 'sudo gitlab-rake gitlab:version' and confirm the version shows 15.5.2, 15.4.4, or 15.3.5 respectively.
  6. 6. Test that the OpenAPI/Swagger viewer functionality works correctly post-upgrade.
Caveat Review GitLab release notes for your upgrade path as major version jumps may require additional migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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