此页面尚未翻译为您的语言。我们正在努力翻译,目前显示英文内容。
💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.
CVE-2026-4527: CSRF in GitLab Allows Unauthorized Jira Subscriptions
平台
gitlab
组件
gitlab
修复版本
18.11.3
CVE-2026-4527 describes a Cross-Site Request Forgery (CSRF) vulnerability discovered in GitLab Community Edition (CE) and Enterprise Edition (EE). This flaw allows an unauthenticated attacker to create unauthorized Jira subscriptions for a targeted user's namespace by exploiting a lack of CSRF protection. The vulnerability impacts GitLab versions from 11.10.0 through 18.11.3, with a fix available in version 18.11.3.
影响与攻击场景翻译中…
The primary impact of CVE-2026-4527 is the potential for unauthorized Jira subscriptions to be created within a GitLab instance. An attacker could craft a malicious link and, if a targeted user clicks it, automatically subscribe that user's namespace to a Jira instance controlled by the attacker. This could lead to sensitive data being inadvertently shared with the attacker's Jira system, potentially exposing project information, code, and other confidential details. While the vulnerability requires user interaction (clicking a malicious link), the lack of authentication needed to trigger the subscription significantly broadens the attack surface. This is similar to other CSRF vulnerabilities where user actions are leveraged to perform unauthorized operations.
利用背景翻译中…
CVE-2026-4527 was published on May 14, 2026. Its severity is rated as MEDIUM (CVSS 6.5). No public Proof-of-Concept (POC) exploits have been identified at the time of writing. There are no indications of active campaigns targeting this vulnerability. Monitor GitLab security advisories and CISA alerts for any updates regarding exploitation attempts.
威胁情报
漏洞利用状态
CISA SSVC
CVSS 向量
这些指标意味着什么?
- Attack Vector
- 网络 — 可通过互联网远程利用,无需物理或本地访问。攻击面最大。
- Attack Complexity
- 低 — 无需特殊条件,可以稳定地利用漏洞。
- Privileges Required
- 无 — 无需认证,无需凭证即可利用。
- User Interaction
- 需要 — 受害者必须打开文件、点击链接或访问特制页面。
- Scope
- 未改变 — 影响仅限于脆弱组件本身。
- Confidentiality
- 高 — 完全丧失机密性,攻击者可读取所有数据。
- Integrity
- 无 — 无完整性影响。
- Availability
- 无 — 无可用性影响。
受影响的软件
弱点分类 (CWE)
时间线
- 已保留
- 发布日期
缓解措施和替代方案翻译中…
The primary mitigation for CVE-2026-4527 is to upgrade GitLab to version 18.11.3 or later. This version includes the necessary CSRF protection to prevent unauthorized Jira subscriptions. If immediate upgrading is not possible, consider implementing a Web Application Firewall (WAF) rule to block requests containing the vulnerable Jira subscription endpoint. Carefully review user permissions and access controls within GitLab to minimize the potential impact if the vulnerability is exploited before patching. There are no specific rollback steps beyond reverting to a previous, patched GitLab version.
修复方法翻译中…
Actualice GitLab a la versión 18.9.7 o posterior, 18.10.6 o posterior, o 18.11.3 o posterior para mitigar la vulnerabilidad CSRF. Esta actualización corrige la falta de protección CSRF que permitía la creación de suscripciones de Jira no autorizadas.
常见问题翻译中…
What is CVE-2026-4527 — CSRF in GitLab?
CVE-2026-4527 is a Cross-Site Request Forgery (CSRF) vulnerability in GitLab CE/EE allowing unauthenticated users to create unauthorized Jira subscriptions for a targeted user's namespace.
Am I affected by CVE-2026-4527 in GitLab?
You are affected if you are running GitLab CE or EE versions 11.10.0 through 18.11.3. Upgrade to version 18.11.3 or later to resolve the issue.
How do I fix CVE-2026-4527 in GitLab?
Upgrade GitLab to version 18.11.3 or later. As a temporary workaround, implement a WAF rule to block requests to the vulnerable Jira subscription endpoint.
Is CVE-2026-4527 being actively exploited?
There are currently no indications of active exploitation campaigns targeting CVE-2026-4527, but continuous monitoring is recommended.
Where can I find the official GitLab advisory for CVE-2026-4527?
Refer to the official GitLab security advisory for CVE-2026-4527 on the GitLab blog: [https://about.gitlab.com/security/advisories/](https://about.gitlab.com/security/advisories/)
立即试用 — 无需账户
上传任何清单文件 (composer.lock, package-lock.json, WordPress 插件列表…) 或粘贴您的组件列表。您立即获得一份漏洞报告。上传文件只是开始:拥有账户后,您将获得持续监控、Slack/电子邮件警报、多项目和白标报告。
拖放您的依赖文件
composer.lock、package-lock.json、requirements.txt、Gemfile.lock、pubspec.lock、Dockerfile...