Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-5952 medium CVSS 4.3

Authorization Flaw in gitlab (CVE-2026-5952)

Summary

Vulnerability in gitlab (CVE-2026-5952). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 18.11.6, 19.0.3, 19.1.1 or later.

Original description

The description as published by the source.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 17.11 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1 that under certain conditions could have allowed an authenticated user with developer-role permissions to bypass package protection rules and overwrite protected Maven package metadata due to incorrect authorization checks.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-5952 has been found in gitlab.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade gitlab to 18.11.6, 19.0.3, 19.1.1 or later.
If unsure, ask your IT team or search "gitlab CVE-2026-5952" on the vendor's site.

CVE-2026-5952 (gitlab) — CWE-863 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 18.11.6, 19.0.3, 19.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Incorrect authorization (CWE-863) exists in gitlab.

📍 Affected scope

Check the vendor advisory for the affected versions of gitlab.

🔥 Severity

Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 18.11.6, 19.0.3, 19.1.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'gitlab' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'gitlab' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で gitlab を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade gitlab to 18.11.6, 19.0.3, 19.1.1

    ステージング環境で 18.11.6, 19.0.3, 19.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami gitlab
[{"type":"SEMVER","events":[{"introduced":"17.11.0"},{"fixed":"18.11.6"},{"introduced":"19.0.0"},{"fixed":"19.0.3"},{"introduced":"19.1.0"},{"fixed":"19.1.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details