CVE-2026-4527: Cross-Site Request Forgery (CSRF) in GitLab

Published May 14, 2026
·
Updated

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.

Affected Software

8 affected components
GitLab GitLab CE>=11.10<18.9.7, >=18.10<18.10.6, >=18.11<18.11.3
GitLab GitLab EE>=11.10<18.9.7, >=18.10<18.10.6, >=18.11<18.11.3
GitLab GitLab>=11.10.0<18.9.7
GitLab GitLab>=11.10.0<18.9.7
GitLab GitLab>=18.10.0<18.10.6
GitLab GitLab>=18.10.0<18.10.6
GitLab GitLab>=18.11.0<18.11.3
GitLab GitLab>=18.11.0<18.11.3

Remediation

Information

Upgrade to versions 18.9.7, 18.10.6, 18.11.3 or above.

Event History

May 14, 2026
CVE Published
via MITRE·05:34 AM
Data Sourced
via MITRE·05:34 AM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·06:16 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-4527?

CVE-2026-4527 has a moderate severity level due to its potential to allow unauthorized actions by unauthenticated users.

2

How do I fix CVE-2026-4527?

To remediate CVE-2026-4527, update GitLab CE/EE to versions 18.9.7, 18.10.6, or 18.11.3 or later.

3

What types of GitLab are affected by CVE-2026-4527?

CVE-2026-4527 affects both GitLab CE (Community Edition) and GitLab EE (Enterprise Edition) from versions 11.10 up to specific later versions.

4

What functionality does CVE-2026-4527 affect in GitLab?

CVE-2026-4527 allows an unauthenticated user to create unauthorized Jira subscriptions for targeted users.

5

Is there a workaround for CVE-2026-4527 before applying the fix?

Currently, there are no documented workarounds for CVE-2026-4527; upgrading to the latest version is recommended.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203