Path traversal flaws of this kind can allow an attacker to reach files and directories outside the intended scope, which is why GitLab is treating this one as urgent. Given the maximum severity rating, administrators should prioritize patching over routine maintenance windows.

Details on affected versions, exploitation status, and any indicators of compromise were not included in the available reporting, so check GitLab's official security advisory for the authoritative version list and fixed releases before upgrading.

• Apply the available GitLab security update as soon as possible.
• Verify your deployed version against the official advisory rather than relying on secondary coverage.
• Monitor GitLab's channels for any follow-up guidance or revised severity information.

Source: BleepingComputer

Has your organization already applied this update, or are you still waiting on a maintenance window?