flawopen.com/Incidentes/GitLab CVE-2026-85706
En un mostrador de biblioteca entregas un papel con el número de estantería para que te traigan el libro. El encargado solo debía buscar en estantes públicos y comprobar tu carné. No hizo ninguna de las dos cosas: cualquiera podía escribir 'el cajón del director' y el encargado se lo traía de inmediato.
The load-bearing idea is that you cannot validate a path by inspecting the string. Blocklisting ../ fails against encoded variants, absolute paths, and symlinks. The only durable check is to fully resolve the path — following every .. and every symlink — and then assert that the resolved result is still underneath the directory you intended.
This is the part teams got wrong. An arbitrary file read on a GitLab server does not just expose source code — it exposes the secrets that the server keeps on disk. Depending on configuration, that can include the instance's shell secret file, SSH host keys, deploy tokens, CI/CD variables and database credentials.
Once those have potentially been read, upgrading closes the hole but leaves the attacker holding valid credentials. Any instance that was internet-reachable and unpatched during the exposure window should be treated as having leaked its secrets, and those secrets rotated.
POST requests to the commits endpoint carrying traversal sequences in the body, especially from unauthenticated sources.The interesting thing about this CVE is not that GitLab shipped a path traversal — it is how ordinary the ingredients were. A parameter named path, a join against a base directory, and an endpoint whose authentication requirement was assumed rather than enforced. Each of those individually appears in a very large number of codebases. The lesson is that path handling and authentication should both be checked at the boundary, mechanically, rather than inherited from the assumption that the surrounding framework already did it.
The advisory scopes the issue to self-managed Community and Enterprise Edition instances. GitLab's own hosted platform was addressed by the vendor directly; the urgent action applies to organisations running their own servers.
Not directly — the primitive is an arbitrary file read. In practice that is often enough to reach code execution indirectly, because the files it exposes include credentials and signing secrets that unlock other systems.
The score reflects that it is remotely reachable, needs no privileges, needs no user interaction, is trivial to exploit, and — because the exposed secrets grant control over other components — its impact is judged to extend beyond the vulnerable component itself.