Vulnerabilities
GitLab 17.9.1/17.8.4/17.7.6 Patch: XSS in k8s Proxy and HTML Injection in Maven Proxy
GitLab released patch versions 17.9.1, 17.8.4, and 17.7.6 on Feb 26 2025 to address high‑severity XSS vulnerabilities in the Kubernetes proxy endpoint and HTML injection in the Maven Dependency Proxy. Self‑managed CE/EE installations must upgrade immediately; GitLab.com and Dedicated customers are already patched.
What happened
On Feb 26 2025 GitLab released patch releases 17.9.1, 17.8.4, and 17.7.6 for both Community and Enterprise editions. The updates fix two high‑severity vulnerabilities: an XSS flaw in the Kubernetes proxy endpoint and an HTML injection flaw in the Maven Dependency Proxy.
Impact
All self‑managed GitLab installations running any of the affected versions are vulnerable. The XSS issue allows attackers to inject malicious scripts via the k8s proxy endpoint, potentially compromising user sessions. The HTML injection flaw can be exploited through the Maven proxy to inject arbitrary HTML into responses.
What to do
- Verify your GitLab version. If you are on 17.9.x, 17.8.x, or 17.7.x and have not yet applied the patch, upgrade to 17.9.1, 17.8.4, or 17.7.6 respectively.
- For omnibus, source, or Helm deployments, follow the standard upgrade procedure documented in the GitLab release notes.
- After upgrading, confirm that the k8s proxy endpoint and Maven proxy are no longer reachable via the vulnerable paths.
- Review audit logs for any suspicious activity during the period before the patch.
Additional notes
GitLab.com is already running the patched version, and Dedicated customers do not need to take action. Security advisories for these fixes will be published on the issue tracker 30 days after release.