GitLab Patches Critical File-Read Flaw After Reports of In-the-Wild Probes

Summary
GitLab patched CVE-2026-85706, a CVSS 10.0 path traversal flaw that could let unauthenticated attackers read files. watchTowr reported in-the-wild probes; GitLab also fixed a critical EE deserialization flaw.
Key points
- CVE-2026-85706 is a path traversal flaw in GitLab’s repository commits API that could allow unauthenticated file reads.
- Affected GitLab CE and EE versions are fixed in 19.1.8, 19.2.6, and 19.3.2.
- watchTowr reported probes against CVE-2026-85706 beginning September 11, 2026; it said the flaw could expose logs and configuration files containing credentials or secrets.
- GitLab also patched CVE-2026-87719, a CVSS 9.9 insecure deserialization issue in GitLab EE that could disclose information.
- GitLab advised organizations to patch exposed self-managed instances promptly or restrict public access; watchTowr recommended reviewing relevant HTTP POST requests for possible exploitation.
Article Details
- Vulnerability Types
- Path traversal
- Insecure deserialization
- Severity
- CVE-2026-85706: CVSS 10.0; CVE-2026-87719: CVSS 9.9.
- Affected Versions
- GitLab CE and EE: all versions from 18.7 before 19.1.8, from 19.2 before 19.2.6, and from 19.3 before 19.3.2
- Exploitation Status
- active
- Exploit Availability
- unknown
- Patch Status
- available
- Workarounds
- For exposed self-managed instances, limit public access if it is not required.
CVE
CVE-2026-85706GitLab · GitLabGitLab has patched CVE-2026-85706, a maximum-severity path traversal flaw in the repository commits API that is already seeing in-the-wild probing and could let unauthenticated attackers read arbitrary files fromCVE-2026-87719GitLab · GitLabThe company also fixed CVE-2026-87719, a critical insecure deserialization issue in GitLab EE, and urged exposed self-managed instances to patch immediately or restrict public access.
