GitLab, the widely adopted DevOps platform, has announced the immediate release of versions 17.8.1, 17.7.3, and 17.6.4 for both its Community Edition (CE) and Enterprise Edition (EE).
These updates address multiple security vulnerabilities and provide critical fixes, underscoring GitLab’s commitment to maintaining the highest security standards.
The vulnerabilities addressed in these updates include a high-severity Stored XSS via Asciidoctor render, a medium-severity issue where a developer could exfiltrate protected CI/CD variables via CI lint, and another medium-severity vulnerability involving cyclic references of epics leading to resource exhaustion.
GitLab strongly encourages self-managed users to upgrade to the latest versions immediately to safeguard their systems.
Are you from SOC/DFIR Teams? - Analyse Malware Files & Links with ANY.RUN Sandox -> Try for Free
Vulnerability Breakdown
1. Stored XSS via Asciidoctor Render – CVE-2025-0314
- CVE-2025-0314 – Improper rendering of specific file types allowed for a cross-site scripting (XSS) attack. This issue affects all versions from 17.2 before 17.6.4, 17.7 before 17.7.3, and 17.8 before 17.8.1.
2. Developer Could Exfiltrate Protected CI/CD Variables via CI Lint – CVE-2024-11931
- CVE-2024-11931 – Developers with specific roles could potentially exploit CI lint to access protected CI/CD variables. This issue affects versions starting from 17.0 before 17.6.4, 17.7 before 17.7.3, and 17.8 before 17.8.1.
3. Cyclic Reference of Epics Leads to Resource Exhaustion – CVE-2024-6324
- CVE-2024-6324 – Creating cyclic references between epics could result in denial-of-service (DoS) attacks. This issue impacts versions starting from 15.7 before 17.6.4, 17.7 before 17.7.3, and 17.8 before 17.8.1.
GitLab has already deployed these updates on GitLab.com, meaning users on the hosted platform are automatically protected. GitLab Dedicated customers do not need to take action. However, self-managed GitLab users are urged to:
- Upgrade to one of the patched versions (17.8.1, 17.7.3, or 17.6.4) immediately.
- Follow best practices for securing GitLab instances, which are outlined in GitLab’s official blog.
GitLab remains steadfast in prioritizing security by addressing vulnerabilities through timely patches.
Security issues are made public 30 days after patch releases to ensure transparency while protecting vulnerabilities during the critical update window.
Integrating Application Security into Your CI/CD Workflows Using Jenkins & Jira -> Free Webinar
