GitLab has patched a maximum-severity flaw that could let an unauthenticated attacker run arbitrary code on self-managed instances, with the bug present in every release dating back to 2014. The October 21 fix supersedes an earlier October 12 patch that only covered newer versions, so administrators who already updated still need to apply the new release. Self-hosted GitLab deployments that haven't upgraded remain exposed to full server compromise.
// source: thehackernews.com ↗