A critical cross-site scripting vulnerability in GitLab CE/EE allows unauthenticated attackers to execute unauthorized actions on behalf of other users, posing a significant risk to environment integrity.

This is a cross-site scripting (CWE-79) flaw residing in the Swagger UI component. The vulnerability allows an unauthenticated attacker to inject malicious scripts, potentially leading to unauthorized actions performed in the context of another user session.

The ability for an unauthenticated attacker to perform actions as another user represents a severe risk to data integrity and account security. Given the CVSS score of 8.0 (High), this vulnerability could lead to unauthorized administrative modifications or sensitive data exposure. The impact is elevated because the flaw resides in the Swagger UI, a commonly accessed component for API documentation and testing.

Immediate Action: Upgrade all instances of GitLab CE/EE to versions 18.4.6, 18.5.4, 18.6.2 or later to apply the necessary security patches.

Proactive Monitoring: Monitor server access logs for anomalous requests directed at Swagger UI endpoints or suspicious script injection patterns.

Compensating Controls: Deploy a Web Application Firewall (WAF) with updated rulesets designed to detect and block cross-site scripting attempts targeting API documentation interfaces.

Public Exploit Available: Yes, a published proof-of-concept exists (attributed to the HackerOne report linked in the CVE references).

The presence of a public proof-of-concept for an unauthenticated cross-site scripting vulnerability makes this a high priority for remediation. Security teams should immediately verify their GitLab version and apply the vendor-provided patches. Failure to patch these versions exposes the organization to potential account takeover and unauthorized API manipulation.