CVE-2026-85706 GitLab Community Edition and Enterprise Edition: file path flaw
In plain words: The program can be tricked into reading or writing files outside the folder it should stay in. Leaks files such as passwords and settings, or overwrites important ones.
Confirmed exploited by CISA on · US federal patch deadline Sep 14, 2026
What to do
- Install GitLab's security update for Community Edition and Enterprise Edition. If no update exists, follow the vendor's workaround or stop using the product until one ships.
- Patch edge devices first — attackers often start scanning for them within hours of a fix.
- Never expose the device's admin page to the internet.
- After patching a device that was exposed, follow the vendor's compromise checks, end active sessions and change passwords.
Who is affected
Work IT. Aimed mostly at company systems — you are affected through the companies you use, not your own phone.
What's at risk: They face the internet and guard the whole network, so a flaw here can hand attackers a way in — and these devices usually run no antivirus, so break-ins go unnoticed.
The details
- Official name
- GitLab Community Edition and Enterprise Edition Path Traversal Vulnerability
- Product
- GitLab Community Edition and Enterprise Edition
- CISA description
- 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.
- Type of flaw
- File path flaw (CWE-35)
- Confirmed exploited
- Sep 11, 2026
- US federal patch deadline
- Sep 14, 2026
Ask Cleus about it
Ask about a vulnerability, an update, a weird message, or the news. Plain-word answers, free, no account.
Answering about CVE-2026-85706 ·
Questions about CVE-2026-85706
Is CVE-2026-85706 being exploited?
Yes. CISA added CVE-2026-85706 to its Known Exploited Vulnerabilities catalog on Sep 11, 2026, which means there is reliable evidence of real-world attacks.
How do I fix CVE-2026-85706?
Install GitLab's security update for Community Edition and Enterprise Edition. If no update exists, follow the vendor's workaround or stop using the product until one ships. Patch edge devices first — attackers often start scanning for them within hours of a fix.
Am I affected by CVE-2026-85706?
Only if you use GitLab Community Edition and Enterprise Edition. Aimed mostly at company systems — you are affected through the companies you use, not your own phone.