CVE-2026-97229: Critical Unauthenticated Remote Code Execution in GitLab
A critical flaw (CVE-2026-97229) has been disclosed in Unauthenticated.
A critical flaw (CVE-2026-97229) has been disclosed in Unauthenticated.
The affected service is reachable from the network without authentication.
Unauthenticated may already be doing an ordinary job in your environment while also being reachable from a network an attacker can access.
Anyone running Unauthenticated is exposed, and because this is reachable without authentication, exposure doesn't depend on a user doing anything.
What an attacker actually gains: successful exploitation allows the attacker to execute code with the permissions of the affected process.
Being reachable without authentication is what moves this from 'patch eventually' to 'patch now' -- there's no login screen standing between an attacker and the vulnerable code.
This is tracked as CVE-2026-97229 and rated critical severity, which is the identifier to use when checking vendor guidance.
Confirm whether Unauthenticated is present anywhere in your asset and software inventory.
No exploitation has been reported yet, but that status can change, so keep watching vendor guidance while you remediate.
What happened
A critical flaw (CVE-2026-97229) has been disclosed in Unauthenticated.
The affected service is reachable from the network without authentication.
Unauthenticated may already be doing an ordinary job in your environment while also being reachable from a network an attacker can access.
Who is affected
Anyone running Unauthenticated is exposed, and because this is reachable without authentication, exposure doesn't depend on a user doing anything.
Why it matters
What an attacker actually gains: successful exploitation allows the attacker to execute code with the permissions of the affected process.
Being reachable without authentication is what moves this from 'patch eventually' to 'patch now' -- there's no login screen standing between an attacker and the vulnerable code.
Technical details
This is tracked as CVE-2026-97229 and rated critical severity, which is the identifier to use when checking vendor guidance.
What security teams should do
Confirm whether Unauthenticated is present anywhere in your asset and software inventory.
No exploitation has been reported yet, but that status can change, so keep watching vendor guidance while you remediate.