What is GitLab CVE-2026-85706?
GitLab's patch release notes say that under certain conditions, an unauthenticated user could read arbitrary files from a GitLab server because of improper path confinement and missing authentication in the repository commits API. GitLab rates it CVSS 3.1 10.0 and released fixes on September 10, 2026, later adding backports.
GitLab.com and GitLab Dedicated were already patched, so only self-managed installations need action. CISA added CVE-2026-85706 to its Known Exploited Vulnerabilities catalog on September 11, 2026, with a September 14 due date. GitLab also released detections to help self-managed customers spot exploitation attempts.
Which GitLab versions are affected?
- Self-managed GitLab CE and EE from 18.7 before 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6 and 19.3 before 19.3.2.
- Fixed in 19.3.2, 19.2.6 and 19.1.8, with backports in 19.0.9 and 18.11.12.
- Not affected: GitLab.com and GitLab Dedicated.
How to check if you're affected
- Check each self-managed instance's version on the
/helppage or the Admin dashboard. - Run the detections GitLab published with the release to look for exploitation attempts.
- Review which files on the server hold secrets, such as
gitlab-secrets.jsonand configuration files, and whether they could have been read.
What to do now
- Upgrade every self-managed instance to a fixed version. GitLab lists no workaround.
- If the detections fire, rotate secrets stored on the server and review access logs.
- Keep self-managed GitLab off the public internet where possible, or behind an identity-aware proxy.
Why a file read on a code host is serious
A source code server holds more than code: configuration files, runner registration tokens, integration credentials and the secrets used to encrypt its own data. Reading the right file can turn a read-only bug into full control of repositories and pipelines. Patch code hosts as fast as production apps, and keep their own secrets out of readable paths.
Where Nullify fits
How Nullify Covers This Class of Attack
Nullify is threat-aware: when an actively exploited vulnerability affects technologies you use, related findings move up your backlog and serious disclosures trigger a threat investigation. Patching self-hosted platforms stays with the team that runs them.
This is a patch for a self-hosted platform, usually owned by an IT or platform team.
Frequently Asked Questions
Which GitLab versions fix CVE-2026-85706?
GitLab 19.3.2, 19.2.6 and 19.1.8, released September 10, 2026, plus backports in 19.0.9 and 18.11.12. GitLab.com and GitLab Dedicated were already patched, so only self-managed instances need upgrading.
What does GitLab CVE-2026-85706 allow?
Under certain conditions, an unauthenticated user can read arbitrary files from a self-managed GitLab server through the repository commits API, because of a path traversal and missing authentication check.
Is CVE-2026-85706 exploited in the wild?
Yes. CISA added CVE-2026-85706 to its Known Exploited Vulnerabilities catalog on September 11, 2026, which means it has evidence of active exploitation. It gave US federal civilian agencies until September 14 to fix it. Treat exposed self-managed GitLab instances as urgent.
Update Log
- Nov 17, 2026: page published from the primary sources linked above.