CYBERSECURITYTRACKER
Permanent story citation

Critical GitLab Flaw (CVSS 10.0) Could Allow Unauthenticated RCE Across 12 Years of Releases

This page keeps the story as Cybersecurity Tracker first published it. If the tracker later corrects it, the correction appears below the original and never replaces it.

Back to newsStory 10959

As cited

Copy frozen at (site build).

vulnerabilities

Critical GitLab Flaw (CVSS 10.0) Could Allow Unauthenticated RCE Across 12 Years of Releases

GitLab released patches on October 21, 2026 for a critical remote code execution (RCE) vulnerability affecting versions dating back to 7.0 from 2014. The flaw allows unauthenticated attackers to execute code on self-managed servers, and an earlier October 12 patch covered only recent versions 19.2 and later, requiring administrators to update again.

Why it matters: Self-managed GitLab administrators running any version from 7.0 onward must apply the October 21 patches immediately to prevent unauthorized code execution, even if they recently patched on October 12.

VendorsGitLab
Source published
First seen by Cybersecurity Tracker

Source attribution

Correction

Correction recorded as of .

vulnerabilities

Critical GitLab Flaw (CVSS 10.0) Could Allow Unauthenticated RCE Across 12 Years of Releases

GitLab released patches on October 21, 2026 for a critical remote code execution (RCE) vulnerability affecting versions dating back to 7.0 from 2014. The flaw allows unauthenticated attackers to execute code on self-managed servers, and an earlier October 12 patch covered only recent versions 19.2 and later, requiring administrators to update again.

Why it matters: Self-managed GitLab administrators running any version from 7.0 onward must apply the October 21 patches immediately to prevent unauthorized code execution, even if they recently patched on October 12.

VendorsGitLab
Source published
First seen by Cybersecurity Tracker

Source attribution

Glossary