このページはまだあなたの言語に翻訳されていません。翻訳作業中のため、英語でコンテンツを表示しています。

💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.

MEDIUMCVE-2026-4527CVSS 6.5

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 KEVNO
インターネット露出

CISA SSVC

悪用状況none
自動化可能no
技術的影響partial

CVSS ベクトル

脅威インテリジェンス· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N6.5MEDIUMAttack VectorNetwork攻撃者がターゲットに到達する方法Attack ComplexityLow悪用に必要な条件Privileges RequiredNone攻撃に必要な認証レベルUser InteractionRequired被害者の操作が必要かどうかScopeUnchanged影響コンポーネント外への波及ConfidentialityHigh機密データ漏洩のリスクIntegrityNone不正データ改ざんのリスクAvailabilityNoneサービス障害のリスクnextguardhq.com · CVSS v3.1 基本スコア
これらのメトリクスの意味は?
Attack Vector
ネットワーク — インターネット経由でリモートから悪用可能。物理・ローカルアクセス不要。
Attack Complexity
低 — 特別な条件不要。安定して悪用可能。
Privileges Required
なし — 認証不要。資格情報なしで悪用可能。
User Interaction
必要 — 被害者がファイルを開く、リンクをクリックするなどのアクションが必要。
Scope
変化なし — 影響は脆弱なコンポーネントのみ。
Confidentiality
高 — 機密性の完全喪失。全データが読み取り可能。
Integrity
なし — 完全性への影響なし。
Availability
なし — 可用性への影響なし。

影響を受けるソフトウェア

コンポーネントgitlab
ベンダーGitLab
最小バージョン11.10.0
最大バージョン18.11.3
修正版18.11.3

弱点分類 (CWE)

タイムライン

  1. 予約済み
  2. 公開日

緩和策と回避策翻訳中…

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/)

あなたのプロジェクトは影響を受けていますか?

依存関係ファイルをアップロードすれば、このCVEや他のCVEがあなたに影響するか即座にわかります。

scanZone.liveBadgescanZone.eyebrow

今すぐ試す — アカウント不要

Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.

手動スキャンSlack/メールアラートContinuous monitoringホワイトラベルレポート

依存関係ファイルをドラッグ&ドロップ

composer.lock、package-lock.json、requirements.txt、Gemfile.lock、pubspec.lock、Dockerfile...