CVE-2026-4527 Cross-Site Request Forgery (CSRF) in GitLab
An unauthenticated attacker can force a victim to create unauthorized Jira subscriptions via a crafted link due to missing CSRF protection in GitLab.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-4527?
CVE-2026-4527 is a medium-severity vulnerability in Gitlab Gitlab, published on 14 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 11.10 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an unauthenticated user to create unauthorized Jira subscriptions for a targeted user's namespace via a specially crafted link due to missing CSRF protection.
Weakness: CWE-352
Which versions are affected by CVE-2026-4527?
1 open source package ship an affected version, including gitlab. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
gitlab Bitnami | From 11.10.0 | 18.9.7, 18.10.6, 18.11.3 |
Products include Gitlab Gitlab.
How do I fix CVE-2026-4527?
Upgrade gitlab to a fixed version for your release line: 18.9.7, 18.10.6 or 18.11.3.
Is CVE-2026-4527 being exploited?
There is no known exploitation of CVE-2026-4527 in the wild and no public exploit code.
Other vulnerabilities in Gitlab Gitlab
- CVE-2026-97229 GitLab Community Edition and Enterprise Edition Integer Overflow or Wraparound
- CVE-2026-85706 GitLab Community Edition and Enterprise Edition Path Traversal
- CVE-2023-7028 GitLab Community and Enterprise Editions Improper Access Control
- CVE-2021-22205 GitLab Community and Enterprise Editions Remote Code Execution
- CVE-2021-39935 GitLab Community and Enterprise Editions Server-Side Request Forgery (SSRF)
Sources
Also known as BIT-gitlab-2026-4527, GHSA-rw3w-8j7h-fwr2, UBUNTU-CVE-2026-4527.