GitLab Patch Release: 18.7.1, 18.6.3, 18.5.5
On January 7, 2026, we released versions 18.7.1, 18.6.3, 18.5.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 Stored Cross-site Scripting issue in GitLab Flavored Markdown placeholders impacts GitLab CE/EE High Cross-site scripting issue in Web IDE impacts GitLab CE/EE High Missing Authorization issue in Duo Workflows API impacts GitLab EE High Denial of Service issue in import functionality impacts Git
CSIRTS triage
- What
- These versions contain important bug and security fixes.
- Who is affected
- All self-managed GitLab installations.
- Urgency
- Remediation is critical as these versions address high-severity vulnerabilities.
- Action
- Upgrade to one of the patched versions immediately.
AI-assisted analysis generated from the source advisory — verify against the original.
⚡ Watch GitLab Community Edition and Enterprise Edition
Get an email when a new GitLab Community Edition and Enterprise Edition advisory drops — max one per day, one-click unsubscribe.
Details
Original advisory: https://docs.gitlab.com/releases/patches/patch-release-gitlab-18-7-1-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-92220.38% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 32% of all EPSS-scored CVEs.
- Low exploitation riskCVE-2025-137610.63% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 47% of all EPSS-scored CVEs.
- Low exploitation riskCVE-2025-137720.39% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 33% of all EPSS-scored CVEs.
- Low exploitation riskCVE-2025-105690.49% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 40% of all EPSS-scored CVEs.
- Low exploitation riskCVE-2025-137810.41% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 35% of all EPSS-scored CVEs.
- Low exploitation riskCVE-2025-112460.40% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 33% of all EPSS-scored CVEs.
- Low exploitation riskCVE-2025-39500.23% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 14% of all EPSS-scored CVEs.
- Low exploitation riskCVE-2025-650180.26% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 18% of all EPSS-scored CVEs.
- Low exploitation riskCVE-2025-647200.42% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 35% of all EPSS-scored CVEs.
Referenced CVEs
| CVE | CSIRTS overview | External |
|---|---|---|
| CVE-2025-9222 | coverage & exploitation status | NVD · CVE.org |
| CVE-2025-13761 | coverage & exploitation status | NVD · CVE.org |
| CVE-2025-13772 | coverage & exploitation status | NVD · CVE.org |
| CVE-2025-10569 | coverage & exploitation status | NVD · CVE.org |
| CVE-2025-13781 | coverage & exploitation status | NVD · CVE.org |
| CVE-2025-11246 | coverage & exploitation status | NVD · CVE.org |
| CVE-2025-3950 | coverage & exploitation status | NVD · CVE.org |
| CVE-2025-65018 | coverage & exploitation status | NVD · CVE.org |
| CVE-2025-64720 | coverage & exploitation status | NVD · CVE.org |
Same CVEs, other sources
How other CERTs, PSIRTs and databases cover the vulnerabilities in this advisory.
- medium[UPDATE] [medium] libpng: Multiple vulnerabilitiescert-bund
- criticalGitLab Patch Release: 18.7.1, 18.6.3, 18.5.5gitlab
More from GitLab Security Releases
- criticalGitLab Critical Patch Release: 19.2.4, 19.1.6, 19.0.8, 18.11.112026-08-17
- criticalGitLab Critical Patch Release: 19.2.4, 19.1.6, 19.0.8, 18.11.112026-08-17
- criticalGitLab Patch Release: 19.2.2, 19.1.4, 19.0.62026-08-12
- criticalGitLab Patch Release: 19.2.2, 19.1.4, 19.0.62026-08-12
- unknownGitLab Patch Release: 18.11.92026-08-06