Exploited vulnerabilities / CVE-2026-85706
Confirmed exploited · authentication bypass · GitLab Community Edition and Enterprise EditionCVE-2026-85706
GitLab Community Edition and Enterprise Edition authentication bypass, confirmed exploited in the wild.
GitLab Community Edition and Enterprise Edition contains a path traversal vulnerability that allows an unauthenticated user to read arbitrary files due to an improper path confinement and missing authentication enforcement in the repository commits API.
| CISA's name for it | GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability |
|---|---|
| Vendor and product | GitLab · Community Edition and Enterprise Edition |
| Type | authentication bypass · CWE-35 |
| Exploited | Confirmed by CISA listed 11 September 2026 |
| Likelihood | one of the most likely to be exploited of every vulnerability tracked |
| Deadline | 14 September 2026 · already passed |
| Used in ransomware | Not reported |
| Advisories | docs.gitlab.com ↗ · www.cisa.gov ↗ · www.cisa.gov ↗ · nvd.nist.gov ↗ |
Three steps, in this order
Apply the vendor fix and restart the affected service.
Put the login or management interface behind a VPN or allow-list; a bypass makes passwords irrelevant.
Rotate credentials and session keys the product holds, and review accounts and configuration changes since the listing date.
| CISA's required action | Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. |
|---|
Know before someone else finds it
Threat Landscape Monitoring fingerprints the software your internet-facing hosts disclose and matches it, every day, against this list and the exploitation scores. When a new entry touches something you run, you are told once, with the host and the fix. The free plan covers one domain.
CVE-2026-85706 in short
Is CVE-2026-85706 being exploited?
Yes. CISA added CVE-2026-85706 to its Known Exploited Vulnerabilities catalogue on 11 September 2026, which it does only on evidence of exploitation in the wild.
What is the CISA deadline for CVE-2026-85706?
US federal agencies must remediate it by 14 September 2026. Everyone else should treat that date as the latest safe point to patch an internet-facing system.
How likely is CVE-2026-85706 to be exploited in the next 30 days?
FIRST's Exploit Prediction Scoring System gives it 97%, the 99th percentile of every CVE it scores.
How do I fix CVE-2026-85706?
Apply the vendor fix and restart the affected service. Put the login or management interface behind a VPN or allow-list; a bypass makes passwords irrelevant. Rotate credentials and session keys the product holds, and review accounts and configuration changes since the listing date.
Other GitLab vulnerabilities being exploited
| CVE | Product | Type | Listed |
|---|---|---|---|
| CVE-2026-97229 | Community Edition and Enterprise Edition | remote code execution | 29 October 2026 |
| CVE-2021-22175 | GitLab | server-side request forgery | 18 February 2026 |
| CVE-2021-39935 | Community and Enterprise Editions | server-side request forgery | 3 February 2026 |
Sources: CISA Known Exploited Vulnerabilities catalogue (released 10 November 2026) and FIRST EPSS. Page compiled automatically by SAK T.L.M, the threat-intelligence tool of SAK T.E.C, on 13 November 2026.