{"id":"gitlab-file-read-attacks-sep-2026","category":"patch","status":"closed","title":"GitLab CE/EE file-read flaw CVE-2026-85706 exploited; fixes and older-branch backports available","tldr":"Attackers have exploited a GitLab flaw that lets them read server files without logging in. Organisations hosting GitLab themselves should update and investigate possible exposure. GitLab.com and GitLab Dedicated are patched.","summary":"CVE-2026-85706 affects GitLab Community Edition and Enterprise Edition servers that organisations operate themselves. Missing access checks and incorrect file-path restrictions in the repository commits API can let someone read server files without signing in. GitLab rates it critical, with a CVSS score of 10.0. Fixes arrived on 10 September, and CISA confirmed exploitation the next day. GitLab added fixes for older 18.11 and 19.0 installations on 23 September. All affected supported branches have fixes; unsupported 18.7–18.10 branches have no fixed build and require an upgrade. GitLab.com and GitLab Dedicated are patched. Updating prevents further exploitation but does not resolve any earlier disclosure. GitLab's investigation guidance distinguishes attempted access from actual disclosure and recommends replacing credentials shown to have leaked. The reviewed sources do not establish how many organisations lost data or that attacks have ended.","action":"GitLab.com and GitLab Dedicated users have nothing to update for this flaw because GitLab has patched those services. If your business hosts GitLab itself, ask IT to install the latest patch on a supported branch; the first fixes were 19.3.2, 19.2.6 and 19.1.8, with later backports 19.0.9 and 18.11.12. Ask IT to preserve logs before restarting, investigate disclosure using GitLab's guidance and replace any exposed credentials.","product":"GitLab Community Edition and Enterprise Edition","audience":"work","severity":"critical","patch":"patched","exploited":true,"cves":["CVE-2026-85706"],"tags":["gitlab","path-traversal","file-disclosure","authentication-bypass","actively-exploited"],"affected":["GitLab CE/EE: all versions from 18.7 before 18.11.12","GitLab CE/EE: 19.0 before 19.0.9","GitLab CE/EE: 19.1 before 19.1.8","GitLab CE/EE: 19.2 before 19.2.6","GitLab CE/EE: 19.3 before 19.3.2"],"fixed":["GitLab CE/EE 18.11.12","GitLab CE/EE 19.0.9","GitLab CE/EE 19.1.8","GitLab CE/EE 19.2.6","GitLab CE/EE 19.3.2"],"matches":[],"sources":[{"kind":"advisory","title":"GitLab Critical Patch Release: 19.3.2, 19.2.6, 19.1.8","url":"https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-2-released/","by":"GitLab","date":"2026-09-10"},{"kind":"advisory","title":"GitLab Critical Patch Release: 19.0.9, 18.11.12","url":"https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-0-9-released/","by":"GitLab","date":"2026-09-23"},{"kind":"advisory","title":"Validating whether a file was actually exfiltrated via CVE-2026-85706 using Workhorse written_bytes","url":"https://support.gitlab.com/hc/en-us/articles/30371082139164-Validating-whether-a-file-was-actually-exfiltrated-via-CVE-2026-85706-using-Workhorse-written-bytes","by":"GitLab","date":"2026-10-08"},{"kind":"advisory","title":"GitLab release and maintenance policy","url":"https://docs.gitlab.com/policy/maintenance/","by":"GitLab","date":""},{"kind":"research","title":"CVE-2026-85706: Critical GitLab Path Traversal Exploited in the Wild","url":"https://www.rapid7.com/blog/post/etr-cve-2026-85706-critical-gitlab-path-traversal-exploited-in-the-wild/","by":"Rapid7","date":"2026-09-14"},{"kind":"news","title":"GitLab urges users to patch max severity path traversal flaw","url":"https://www.bleepingcomputer.com/news/security/gitlab-urges-users-to-patch-max-severity-path-traversal-flaw/","by":"BleepingComputer","date":"2026-09-11"},{"kind":"news","title":"GitLab CVE-2026-85706: Four Lines Still Without a Fix","url":"https://endoflife.ai/article-gitlab-cve-2026-85706-six-lines-without-a-fix","by":"endoflife.ai","date":"2026-10-18"},{"kind":"news","title":"Over 1,000 GitLab servers vulnerable to ongoing RCE attacks","url":"https://www.bleepingcomputer.com/news/security/over-1-000-gitlab-servers-vulnerable-to-code-execution-attacks/","by":"BleepingComputer","date":"2026-11-02"}],"started":"2026-09-10","closed":"2026-10-08","created":"2026-11-03T22:10:40.902Z","updated":"2026-11-03T22:10:40.902Z","cve_notes":[{"cve":"CVE-2026-85706","name":"GitLab repository commits API unauthenticated file read","what":"Incorrect file-path restrictions and missing authentication checks in GitLab CE/EE's repository commits API let an attacker read arbitrary server files without logging in, under certain conditions.","severity":"critical","cvss":10}],"timeline":[{"at":"2026-10-08","added":"2026-11-03T22:00:26.134Z","kind":"vendor-revised","text":"GitLab updated its investigation guidance: a request that reads a file does not necessarily disclose its contents. Administrators should preserve logs before restarting and examine what was actually returned before deciding which credentials to replace.","url":"https://support.gitlab.com/hc/en-us/articles/30371082139164-Validating-whether-a-file-was-actually-exfiltrated-via-CVE-2026-85706-using-Workhorse-written-bytes","by":"GitLab","patch":null},{"at":"2026-09-23","added":"2026-11-03T22:00:26.134Z","kind":"new-fix","text":"GitLab released 19.0.9 and 18.11.12, bringing the fix to two older branches outside its normal maintenance policy.","url":"https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-0-9-released/","by":"GitLab","patch":null},{"at":"2026-09-11","added":"2026-11-03T22:00:26.134Z","kind":"cisa-added","text":"CISA added CVE-2026-85706 to its Known Exploited Vulnerabilities catalogue, confirming exploitation. It required affected US federal civilian agencies to remediate by 14 September.","url":"https://www.rapid7.com/blog/post/etr-cve-2026-85706-critical-gitlab-path-traversal-exploited-in-the-wild/","by":"Rapid7","patch":null},{"at":"2026-09-10","added":"2026-11-03T22:00:26.134Z","kind":"disclosed","text":"GitLab disclosed CVE-2026-85706 and released CE/EE 19.3.2, 19.2.6 and 19.1.8. The flaw lets someone read server files without logging in; GitLab.com was already patched and GitLab Dedicated customers needed no action.","url":"https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-3-2-released/","by":"GitLab","patch":"patched"}],"url":"https://hard.fyi/live/gitlab-file-read-attacks-sep-2026/","json":"https://hard.fyi/api/live?id=gitlab-file-read-attacks-sep-2026"}