Vulnerability in gitlab (CVE-2026-1322)
Summary
Vulnerability in gitlab (CVE-2026-1322). Confidential information can be exposed externally. Mitigation: upgrade to 18.9.7, 18.10.6, 18.11.3 or later.
Original description
The description as published by the source.
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.0 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user with a read_api scoped OAuth application to create issues and add comments to issues in private projects due to improper authorization.
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-1322 has been found in gitlab.
Confidential information can be exposed externally. CVSS score: 6.8/10.
What to do: upgrade gitlab to 18.9.7, 18.10.6, 18.11.3 or later.
If unsure, ask your IT team or search "gitlab CVE-2026-1322" on the vendor's site.
CVE-2026-1322 (gitlab) — CWE-840 / CVSS v3 6.8
Attack vector: remote (network-reachable) / no user interaction
Patched: 18.9.7, 18.10.6, 18.11.3 — 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.
A vulnerability (CWE-840) exists in gitlab.
Check the vendor advisory for the affected versions of gitlab.
Severity: Medium (CVSS 6.8/10). Confidential information can be exposed externally.
Update to 18.9.7, 18.10.6, 18.11.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify exposure identify
grep -r 'gitlab' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
gitlabを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade gitlab to 18.9.7, 18.10.6, 18.11.3ステージング環境で 18.9.7, 18.10.6, 18.11.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-1322 gitlab
References
- web nvd.nist.gov
- web hackerone.com
- web about.gitlab.com
- web gitlab.com
- web github.com
- web about.gitlab.com