45
60
60
60
60
60
60
60
60
60
60
45
CISA: Hackers now exploit max severity GitLab flaw in attacks
CISA added max-severity GitLab CVE-2026-85706 to its exploited-flaws catalog after watchTowr observed probing of unpatched servers.
CISA added CVE-2026-85706, a maximum-severity GitLab flaw caused by missing authentication enforcement and improper path confinement in the repository commits API, to its actively exploited vulnerabilities catalog. Unauthenticated attackers can read credentials, secrets, and arbitrary files from vulnerable servers via a single HTTP request. GitLab patched the issue in CE/EE versions 19.3.2, 19.2.6, and 19.1, and federal agencies have three days to remediate under BOD 26-04. watchTowr reported in-the-wild probes for unpatched GitLab servers, and this is the fourth GitLab vulnerability CISA has tagged as actively exploited since November 2021.
30
60
45
50
60
60
60
60
60
60
60
60
60
60
45
60
60
60
A maximum severity GitLab flaw could turn your CI/CD server into an attacker’s treasure trove
GitLab patched maximum-severity CVE-2026-85706, an unauthenticated path traversal enabling arbitrary file reads; CISA added it to KEV amid observed in-the-wild probes.
CVE-2026-85706 is a CVSS 10.0 path traversal in GitLab's repository commits API caused by improper confinement and missing authentication enforcement, allowing arbitrary file reads in a single unauthenticated HTTP request. It affects GitLab CE and EE versions 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2, and was reported via GitLab's HackerOne bug bounty. CISA added the flaw to its Known Exploited Vulnerabilities catalog, and watchTowr Intel reports already observing in-the-wild probes; GitLab is used by roughly 50% of the Fortune 100 with over 50 million registered users. Defenders are advised to patch immediately, rotate any exposed secrets, and hunt logs for HTTP POST requests to /api/v4/projects/{id}/repository/commits/ URIs containing file.path parameters.
88
60
60
60
60
60
60
60
60
60