2025/4/23 アナウンスされたセキュリティリリース情報。「優先度：高」が３件で クロスサイト スクリプティング (XSS)脅威に対する修正などが発表されています。また、今回の影響対象には、EE(Enterprise版）だけではなくCE(Comunity版）も含まれる事項もあるため、影響対象の環境が大きい可能性があります。ぜひ確認ください。
以下 GitLab Patch Release: 17.11.1, 17.10.5, 17.9.7 冒頭部分翻訳および原文を掲載します。
原文へのリンクは上記もしくは以下URLから
https://about.gitlab.com/releases/2025/04/23/patch-release-gitlab-17-11-1-released/?utm_medium=email&utm_source=marketo&utm_campaign=security+release+email&April+23+2025
///////////////////////////////////////////////////////////////
（翻訳）
GitLab パッチ リリースの詳細: GitLab Community Edition (CE) および Enterprise Edition (EE) の 17.11.1、17.10.5、17.9.7。
本日、GitLab Community Edition (CE) および Enterprise Edition (EE) のバージョン 17.11.1、17.10.5、17.9.7 をリリースします。
これらのバージョンには重要なバグ修正とセキュリティ修正が含まれています。すべてのセルフマネージドGitLabインストールをこれらのバージョンに直ちにアップグレードすることを強くお勧めします。GitLab.comではすでにパッチ適用済みバージョンが稼働しています。GitLab Dedicatedのお客様は、特別な対応は不要です。
GitLabは、脆弱性に対する修正をパッチリリースで提供しています。パッチリリースには、定期リリースと、重大度の高い脆弱性に対するアドホックな緊急パッチの2種類があります。定期リリースは、毎月第2水曜日と第4水曜日に2回リリースされます。詳細については、リリースハンドブックとセキュリティに関するFAQをご覧ください。GitLabのリリースに関するブログ投稿はすべてこちらでご覧いただけます。
セキュリティ修正については、各脆弱性の詳細を記載した問題が、修正されたリリースの 30 日後に問題追跡システムで公開されます 。
GitLabは、お客様に公開されている、またはお客様のデータをホストしているGitLabのあらゆる側面において、最高水準のセキュリティ基準を維持することに尽力しています。セキュリティ対策の一環として、すべてのお客様に、サポート対象バージョンの最新パッチリリースへのアップグレードを強く推奨いたします。GitLab インスタンスのセキュリティ保護に関するベストプラクティスについては、ブログ記事をご覧ください。
推奨されるアクション
下記の問題の影響を受けるバージョンを実行しているすべてのインストールをできるだけ早く最新バージョンにアップグレードすることを強くお勧めします。
製品の特定のデプロイメント タイプ (オムニバス、ソース コード、Helm チャートなど) が指定されていない場合は、すべてのタイプが影響を受けることを意味します。
—————————————————————-
（原文）
Learn more about GitLab Patch Release: 17.11.1, 17.10.5, 17.9.7 for GitLab Community Edition (CE) and Enterprise Edition (EE).
Today we are releasing versions 17.11.1, 17.10.5, 17.9.7 for GitLab Community Edition (CE) and Enterprise Edition (EE).
These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action.
GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases, and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, you can visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here.
For security fixes, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched.
We are committed to ensuring all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. As part of maintaining good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post.
Recommended Action
We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible.
When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, this means all types are affected.
Security fixes
Table of security fixes
Cross Site Scripting (XSS) in Maven Dependency Proxy through CSP directives
An issue has been discovered in GitLab EE that allows for cross-site-scripting attack and content security policy bypass in a user’s browser under specific conditions, affecting all versions from 16.6 prior to 17.9.7, 17.10 prior to 17.10.5, and 17.11 prior to 17.11.1. This is a high severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N, 8.7). It is now mitigated in the latest release and is assigned CVE-2025-1763.
Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.
Cross Site Scripting (XSS) in Maven dependency proxy through cache headers
An issue has been discovered in GitLab EE that allows for cross-site-scripting attack and content security policy bypass in a user’s browser under specific conditions, affecting all versions from 16.6 prior to 17.9.7, 17.10 prior to 17.10.5, and 17.11 prior to 17.11.1. This is a high severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N, 8.7). It is now mitigated in the latest release and is assigned CVE-2025-2443.
Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.
Network Error Logging (NEL) Header Injection in Maven Dependency Proxy Allows Browser Activity Monitoring
An issue has been discovered in GitLab EE/CE that could allow an attacker to track users’ browsing activities, potentially leading to full account take-over, affecting all versions from 16.6 prior to 17.9.7, 17.10 prior to 17.10.5, and 17.11 prior to 17.11.1. This is a high severity issue (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N, 7.7). It is now mitigated in the latest release and is assigned CVE-2025-1908.
Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.
Denial of service (DOS) via issue preview.
An issue has been discovered affecting service availability via issue preview in GitLab CE/EE affecting all versions from 16.7 prior to 17.9.7, 17.10 prior to 17.10.5, and 17.11 prior to 17.11.1. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, 6.5). It is now mitigated in the latest release and is assigned CVE-2025-0639.
Thanks sigitsetiawansss for reporting this vulnerability through our HackerOne bug bounty program.
Unauthorized access to branch names when Repository assets are disabled in the project
An issue has been discovered in access controls could allow users to view certain restricted project information even when related features are disabled in GitLab EE, affecting all versions from 17.7 prior to 17.9.7, 17.10 prior to 17.10.5, and 17.11 prior to 17.11.1. This is a medium severity issue (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N, 4.3). It is now mitigated in the latest release and is assigned CVE-2024-12244.
Thanks mateuszek for reporting this vulnerability through our HackerOne bug bounty program.
Bug fixes
17.11.1
- Put allow_composite_identities_to_run_pipelines behind ff
- Backporting doc fix for Amazon Q
- [BP]last_rollout_failed_at should be set for failures namespaces also
- Fix Amazon Q disconnect for already destroyed app
- Fix string conversion for CI Inputs
- Backport fix for latest DS template in combination with Static Reachability
- Merge branch ‘535633-new-look-causes-attach-file-to-ignore-external_url’ into ‘master’
- Patch in 17.11: Sync Cloud Connector tokens hourly
- Update Workhorse Gitaly client dependency
17.10.5
- Backport ‘fix-ubi-mailroom-location’ into ’17-10-stable’
- backport update-go-grpc-to-1.71.1 to 17-10-stable
- [Backport 17.10] Bulk indexing cron workers should respect pause setting
- [17.10] Backport: Zoekt: Fix incorrect project filtering in Zoekt initial indexing
- Backport: Zoekt: Rollout is considering offline nodes as well
- Backport: Zoekt Newly created indices are instantly evicted
- Backport NoMethodError: zoekt_nodes is null in some instances
- Fix workspaces reconciliation to send inventory config map correctly
- [17.10 Backport] Clean up the FinalizeBackfillCiRunnerMachinesPartitionedTable migration
- Introduce a new gitlab:doctor:encryption_keys task
- Backport “Resolve “/api/v4/todos returns 500 when has wiki todo””
- Update workhorse gitalyclient dependency update backport to 17.10
- [17.10 Backport] Clear session cookie when browser is closed
- Backport AI events backfill from PG to ClickHouse
- Patch in 17.10: Sync Cloud Connector tokens hourly
17.9.7
- Backport setting FIPS and UBI pipeline name to 17-9-stable
- Backport ‘fix-ubi-mailroom-location’ into ’17-9-stable’
- backport update-go-grpc-to-1.71.1 to 17-9-stable
- [17.9 Backport] Clean up the FinalizeBackfillCiRunnerMachinesPartitionedTable migration
- Introduce a new gitlab:doctor:encryption_keys task
- Update workhorse gitalyclient dependency backport to 17.9
Updating
To update GitLab, see the Update page. To update Gitlab Runner, see the Updating the Runner page.
Receive Patch Notifications
To receive patch blog notifications delivered to your inbox, visit our contact us page. To receive release notifications via RSS, subscribe to our patch release RSS feed or our RSS feed for all releases.
We’re combining patch and security releases
This improvement in our release process matches the industry standard and will help GitLab users get information about security and bug fixes sooner, read the blog post here.
///////////////////////////////////////////////////////////////
弊社パートナー様はNetworld Dev Portal アカウント（無料）登録いただくと、GitLabパートナー制度や DevSecOps関連提案資料などのパートナー限定コンテンツがご覧いただけます。
DevSecOps全般、GitLab製品または本サイトについては以下よりお問い合わせ下さい。
