High · published January 14, 2026
⚡ An authenticated user can unleash stored cross-site scripting in GitLab's Kubernetes proxy! This vulnerability affects versions from 15.10 to 18.3.6, 18.4 to 18.4.4, and 18.5 to 18.5.2. 🔥 Think of this as allowing a diner to slip a hidden ingredient into the chef's special. If the chef isn't vigilant, that sneaky ingredient can spoil the whole meal — in this case, your application! An attacker can execute malicious scripts in the context of other users, potentially stealing sensitive data or compromising user sessions. The ripple effect can lead to unauthorized actions and significant data breaches, seriously endangering your project and reputation.
Think of this as allowing a diner to slip a hidden ingredient into the chef's special. If the chef isn't vigilant, that sneaky ingredient can spoil the whole meal — in this case, your application! This vulnerability arises from improper input validation in the Kubernetes proxy functionality, allowing malicious scripts to be stored and executed by other authenticated users. It acts like a loophole that lets bad ingredients into an otherwise secure meal.
An attacker can execute malicious scripts in the context of other users, potentially stealing sensitive data or compromising user sessions. The ripple effect can lead to unauthorized actions and significant data breaches, seriously endangering your project and reputation. To protect your GitLab instance, upgrade immediately to versions 18.3.6, 18.4.4, or 18.5.2, depending on your current version. Regularly audit your input validation processes and consider implementing stricter content security policies to bolster protection. You've got this! Follow these steps and you'll secure your GitLab environment in no time! 🛡️