GitLab reports that an unauthenticated user could read arbitrary files from the server through the repository commits API in GitLab CE and EE. CISA lists CVE-2026-85706 as exploited.
What is affected
GitLab reports a path traversal issue in GitLab Community Edition and Enterprise Edition, tracked as CVE-2026-85706. The weakness is classified as CWE-35. According to GitLab, the following version ranges are affected:
≥ 18.7.0, < 18.11.12≥ 19.0.0, < 19.0.9≥ 19.1.0, < 19.1.8≥ 19.2.0, < 19.2.6≥ 19.3.0, < 19.3.2
The scoring in the public record uses CVSS version 3.1 and rates the issue as critical. The vector describes an attack over the network with low complexity, no privileges and no user interaction, and a changed scope.
What the flaw allows
GitLab states that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server. The vendor attributes this to improper path confinement and missing authentication enforcement in the repository commits API.
In practical terms, a person with network access to an affected instance, and no account on it, could be able to read files stored on the server. Depending on what the server holds, this can include configuration data and other sensitive material. The public record does not describe any further effect, and this advisory does not go beyond what the sources say.
Exploitation
The CISA Known Exploited Vulnerabilities catalogue lists this vulnerability as exploited. CISA added it on 2026-09-11. CISA's stated deadline for US federal agencies to act is 2026-09-14. That deadline applies to those agencies, but it shows how CISA rates the urgency. CISA lists known ransomware use as unknown.
The vulnerability was disclosed on 2026-09-12 according to the facts we hold. We have not analysed or tested the issue ourselves. This summary relies on the vendor, the NVD and CISA.
What to do
Check whether you run GitLab Community Edition or Enterprise Edition in one of the version ranges above, including instances that are only reachable from internal networks. GitLab publishes the fixed releases in its patch release announcement, which is the place to confirm the release that applies to your version line. Apply the vendor's instructions as soon as you can, and treat any exposed instance in an affected range as a priority.
Further detail is available from the GitLab patch release announcement, the NVD entry and the CISA catalogue entry.
What to do
Follow the vendor's instructions in the GitLab patch release announcement, which lists the fixed releases for each affected version line.
- Identify every
GitLab Community Edition and Enterprise Editioninstance in the affected ranges. - Prioritise instances reachable from the internet.
- CISA's required action is to apply mitigations in line with vendor instructions, or to stop using the product if mitigations are unavailable. See the CISA catalogue entry.