GitLab CE/EE is widely used; unauthenticated arbitrary file read (CVSS 10.0) with CISA KEV makes this a high-impact, org‑wide risk.
CVE-2026-85706
Unauthenticated path traversal in GitLab repo commits API allows arbitrary file read.
Is CVE-2026-85706 being exploited?
Yes. CVE-2026-85706 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2026-85706?
CVE-2026-85706 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-85706?
Yes. A fix has been recorded for CVE-2026-85706. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-85706 affect?
CVE-2026-85706 affects GitLab CE/EE 18.7 before 19.1.8, GitLab CE/EE 19.2 before 19.2.6, GitLab CE/EE 19.3 before 19.3.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-85706?
Apply vendor patches immediately or isolate internet‑exposed GitLab instances.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can read arbitrary files on GitLab servers via path traversal, exposing secrets, configs, tokens, and source code.
Immediate action required
- affected>= 18.7 and < 19.1.8
- affected>= 19.2 and < 19.2.6
- affected>= 19.3 and < 19.3.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.