Ce mail provient de l'extérieur, restons vigilants ===================================================================== CERT-Renater Note d'Information No. 2025/VULN470 _____________________________________________________________________ DATE : 24/07/2025 HARDWARE PLATFORM(S): / OPERATING SYSTEM(S): Systems running GitLab versions prior to 18.2.1, 18.1.3, 18.0.5. ===================================================================== https://about.gitlab.com/releases/2025/07/23/patch-release-gitlab-18-2-1-released/ _____________________________________________________________________ GitLab Patch Release: 18.2.1, 18.1.3, 18.0.5 Learn more about GitLab Patch Release: 18.2.1, 18.1.3, 18.0.5 for GitLab Community Edition (CE) and Enterprise Edition (EE). Today, we are releasing versions 18.2.1, 18.1.3, 18.0.5 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, please 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 that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain 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, it means all types are affected. Security fixes Table of security fixes Title Severity Cross-site scripting (XSS) impacts k8s proxy in GitLab CE/EE High Cross-site scripting (XSS) impacts k8s proxy in GitLab CE/EE using CDNs High Exposure of Sensitive Information to an Unauthorized Actor issue impacts GitLab CE/EE Medium Improper Access Control issue impacts GitLab EE Medium Exposure of Sensitive Information to an Unauthorized Actor issue impacts GitLab CE/EE Medium Improper Access Control issue impacts GitLab CE/EE Medium CVE-2025-4700 - Cross-site scripting issue impacts Kubernetes Proxy in GitLab CE/EE GitLab has remediated an issue affecting a Kubernetes proxy feature that, under specific circumstances, could have potentially allowed a successful attacker to trigger unintended content rendering leading to XSS. Impacted Versions: GitLab CE/EE: all versions from 15.10 before 18.0.5, 18.1 before 18.1.3, and 18.2 before 18.2.1. CVSS: 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program. CVE-2025-4439 - Cross-site scripting issue impacts Kubernetes Proxy in GitLab CE/EE using CDNs GitLab has remediated an issue that could have allowed an authenticated user to perform cross-site scripting attacks when the instance is served through certain content delivery networks. Impacted Versions: GitLab CE/EE: all versions from 15.10 before 18.0.5, 18.1 before 18.1.3, and 18.2 before 18.2.1. CVSS: 7.7 (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N) Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program. CVE-2025-7001 - Exposure of Sensitive Information to an Unauthorized Actor issue impacts GitLab CE/EE GitLab has remediated an issue that could have allowed privileged users to access certain resource_group information through the API which should have been unavailable. Impacted Versions: GitLab CE/EE: all versions from 15.0 before 18.0.5, 18.1 before 18.1.3, and 18.2 before 18.2.1. CVSS: 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks iamgk808 for reporting this vulnerability through our HackerOne bug bounty program. CVE-2025-4976 - Improper Access Control issue impacts GitLab EE GitLab has remediated an issue that, under certain circumstances, could have allowed an attacker to access internal notes in GitLab Duo responses. Impacted Versions: GitLab EE: all versions from 17.0 before 18.0.5, 18.1 before 18.1.3, and 18.2 before 18.2.1. CVSS: 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks rogerace for reporting this vulnerability through our HackerOne bug bounty program. CVE-2025-0765 - Exposure of Sensitive Information to an Unauthorized Actor issue impacts GitLab CE/EE GitLab has remediated an issue that could have allowed an unauthorized user to access custom service desk email addresses. Impacted Versions: GitLab CE/EE: all versions from 17.9 before 18.0.5, 18.1 before 18.1.3, and 18.2 before 18.2.1. CVSS: 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks iamgk808 for reporting this vulnerability through our HackerOne bug bounty program. CVE-2025-1299 - Improper Access Control issue impacts GitLab CE/EE GitLab has remediated an issue that, under circumstances, could have allowed an unauthorized user to read deployment job logs by sending a crafted request. Impacted Versions: GitLab CE/EE affecting all versions starting from 15.4 before 18.0.5, all versions starting from 18.1 before 18.1.3, all versions starting from 18.2 before 18.2.1. CVSS: 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks pwnie for reporting this vulnerability through our HackerOne bug bounty program. * Bug fixes 18.2.1 Fix double-path issue for COM_REGISTRY Update VERSION files Backport of '[Agentic Chat] Do not response to NewCheckpoint message' Backport of Delete the search_refactor_membership_filter feature flag Backport of 'Fix S3 compatibility in Workhorse uploads for non-AWS S3 providers' [Backport] Allow users to resume/continue previous chat sessions in Agentic Chat instead of forcing new chat creation. Send workflow metadata for Agentic Chat Backport of Fix Github Import E2E Backport fix for Workhorse race test: ignore EOF error for Duo Workflow send stream 18.1.3 Merge branch 'jk/cache-assets-security-mirror' into 'master' [backport] 'tbulva-zoekt-url-reset' into '18.1' Revert "Merge branch 'cherry-pick-54ec1758' into '18-1-stable-ee'" Merge branch 'dattang/pass-omnibus-package-to-release-environment-pipeline' into 'master' Merge branch 'dattang/run-qa-on-get-release-environment' into '18-1-stable-ee' [backport] Add check for allowlist when configuring Elasticsearch URL Backport of "Backport of 'Disable directory_code_dropdown_updates flag'" Revert "Enable assets caching on security stable branches" Backport of 'Fixed branches loading on group merge request list' Backport of Trigger webhook events on vulnerability dismissal Backport GitLab Exporter 15.6.0 to 18.1.x Update dependency container-registry to v4.23.2-gitlab 18.0.5 [Backport 18.0] Zoekt: Only enable global search when nodes are online Run GET Release Environments on 18-0-stable-ee Backport of 'Fixed branches loading on group merge request list' Backport 'dattang/fix-syntax-release-env-pipeline' into '18-0-stable-ee' [backport to 18.0] Add check for allowlist when configuring Elasticsearch URL Backport of Trigger webhook events on vulnerability dismissal Update dependency container-registry to v4.21.4-gitlab Build Omnibus package for GET Release Environments - 18.0 Merge branch 'cb-fix-prein-version-parse' into '18-0-stable' 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. ========================================================= + CERT-RENATER | tel : 01-53-94-20-44 + + 23/25 Rue Daviel | fax : 01-53-94-20-41 + + 75013 Paris | email:cert@support.renater.fr + =========================================================