GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, under certain conditions, an unauthenticated user could have poisoned a shared cache's OAuth/OIDC discovery document to redirect certain flows to an externally controlled server, due to improper trust of user-supplied values when constructing endpoint URLs in cached discovery responses.
GitLab released fixes on October 21 for a flaw that lets an attacker run code on a self-managed server without logging in, and it affects every version of the software going back to 7.0, released in 2014. The fix matters even for administrators who patched nine days earlier: the October 12 update covered only versions 19.2 and later, and the new fixed versions sit one patch above it, so an…
gbhackers. Thursday, October 22, 2026 Linkedin RSS Twitter gbhackers. • Home • Threats • Cyber Attack • Data Breach • Vulnerability • What is • DFIR • Top 10 Search [](https://gbhackers.com/gitlab-patches-critical-10-0-rce-vulnerability/#) Follow us On Linkedin Discover more Cybersecurity news platform Security flaw patching Information security training CVE/vulnerabilityCyber Security NewsGitLab…
GitLab has released urgent security updates for a critical vulnerability that could let attackers run code on self-managed servers without logging in. Tracked as CVE-2026-110264, the flaw carries the maximum CVSS score of 10.0 and affects both GitLab Community Edition and Enterprise Edition. The company published the fixes on October 21, 2026. The affected code reaches back to GitLab 7.0,…