Tag: cve 2026 85706
6 articles
GitLab Flaw Exploited After Patch Release
A newly patched GitLab flaw, rated a perfect 10.0 in severity, is being exploited by attackers, who can use it to read arbitrary files from vulnerable servers without needing to log in. This path traversal bug in GitLab's repository commits API is especially concerning since it often stores sensitive source code, configuration files, and credentials.
GitLab Flaw Exploited in Wild, Prompting Urgent Patch Push
A critical GitLab bug, CVE-2026-85706, is under active exploitation, putting sensitive files at risk of exposure due to a path traversal vulnerability that allows unauthenticated users to access arbitrary files. GitLab has urgently pushed a patch to fix the flaw, affecting versions CE/EE 18.7 to 19.3.2.
Hackers Exploit GitLab Flaw in Active Attacks
Hackers are actively exploiting a critical GitLab flaw, CVE-2026-85706, that allows them to read sensitive information like credentials and secrets with just a single HTTP request. This vulnerability enables attackers to access arbitrary files, potentially exposing long-lived secrets and confidential data.
GitLab Flaw Draws Widespread Probes Ahead of Patch
GitLab has rushed out emergency patches for two severe flaws in its platform, warning users to upgrade ASAP to avoid potential exploitation. A particularly critical defect, CVE-2026-85706, has been assigned a maximum CVSS score of 10.0, sparking widespread concern.
GitLab Discloses Path Traversal Flaw Exploited in Wild
GitLab has revealed a critical path traversal flaw, CVE-2026-85706, that allows unauthenticated users to access sensitive files on its servers, and security researchers have already spotted attackers probing for vulnerabilities in the wild. This maximum-severity bug, scoring a CVSS 10.0, enables hackers to read arbitrary files, including log files and configuration files.
GitLab Warns Users to Patch Path Traversal Flaw
GitLab is urging users to upgrade immediately to patch a critical path traversal flaw, CVE-2026-85706, that could expose sensitive files to unauthenticated attackers. This maximum-severity vulnerability requires prompt action to protect self-managed GitLab installations.