GitLab Patch Release: 17.8.2, 17.7.4, 17.6.5

criticalCVE-2025-0376 CVE-2024-12379 CVE-2024-3303 CVE-2025-1212 CVE-2024-9870 CVE-2025-0516

On February 12, 2025, we released versions 17.8.2, 17.7.4, 17.6.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, 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 Title Severity A CSP-bypass XSS in merge-request page High Denial of Service due to Unbounded Symbol Creation Medium Exfiltrate content from private issues using Prompt Injection Medium Internal HTTP header leak via route confusion in workhorse Medium SSRF via workspaces Medium Unauthorized Inciden

CSIRTS triage

vendor: GitLab product: GitLabaffected: 17.8.2, 17.7.4, 17.6.5

What: GitLab released critical patch versions containing important bug and security fixes.
Who is affected: All self-managed GitLab installations using affected versions.
Urgency: Remediation is urgent due to the critical nature of the vulnerabilities addressed.
Action: Upgrade to one of the patched versions immediately.

AI-assisted analysis generated from the source advisory — verify against the original.

⚡ Watch GitLab

Get an email when a new GitLab advisory drops — max one per day, one-click unsubscribe.

Details

Source: GitLab Security Releases (INTL · vendor-psirt · site)
Severity: critical
Published: 2025-02-12
Exploitation: Not in CISA KEV at last sync

Original advisory: https://docs.gitlab.com/releases/patches/patch-release-gitlab-17-8-2-released/

Exploitation outlook

EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.

Low exploitation riskCVE-2025-03760.38% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 30% of all scored CVEs.
Low exploitation riskCVE-2024-123790.47% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 38% of all scored CVEs.
Low exploitation riskCVE-2024-33030.37% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 29% of all scored CVEs.
Low exploitation riskCVE-2025-12120.35% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 28% of all scored CVEs.
Low exploitation riskCVE-2024-98700.37% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 29% of all scored CVEs.
Low exploitation riskCVE-2025-05160.28% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 19% of all scored CVEs.
Low exploitation riskCVE-2025-11980.24% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 15% of all scored CVEs.
Low exploitation riskCVE-2025-10420.41% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 33% of all scored CVEs.
Low exploitation riskCVE-2025-15400.22% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 12% of all scored CVEs.

Referenced CVEs

CVE	CSIRTS overview	External
CVE-2025-0376	coverage & exploitation status	NVD · CVE.org
CVE-2024-12379	coverage & exploitation status	NVD · CVE.org
CVE-2024-3303	coverage & exploitation status	NVD · CVE.org
CVE-2025-1212	coverage & exploitation status	NVD · CVE.org
CVE-2024-9870	coverage & exploitation status	NVD · CVE.org
CVE-2025-0516	coverage & exploitation status	NVD · CVE.org
CVE-2025-1198	coverage & exploitation status	NVD · CVE.org
CVE-2025-1042	coverage & exploitation status	NVD · CVE.org
CVE-2025-1540	coverage & exploitation status	NVD · CVE.org

Recent advisories for GitLab Patch Release

A cluster of recent advisories against the same product widens the attack surface — attackers routinely chain freshly published CVEs on one product, so review these together.

criticalGitLab Patch Release: 19.1.2, 19.0.4, 18.11.7gitlab · 2026-07-08
unknownGitLab Patch Release: 18.8.11gitlab · 2026-07-01
unknownGitLab patch release notesgitlab · 2026-07-01
criticalGitLab Patch Release: 19.1.1, 19.0.3, 18.11.6gitlab · 2026-06-24
criticalGitLab Patch Release: 19.0.2, 18.11.5, 18.10.8gitlab · 2026-06-10
unknownGitLab Patch Release: 18.9.8, 18.8.10, 18.7.7, 18.6.8, 18.5.7gitlab · 2026-05-27