Patch Forecast
Yellow warning
Plan into this sprint.

CVE-2026-13319

GitLab: authorisation bypass

Risk score
42/100
CVSS
6.5 v3.1
Exploit chance (30 days)
0.2%
Published
22 Oct 2026

Open in the live forecast Today's forecast

What to know

What it is
GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.10 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, could have allowed an authenticated to read milestone metadata, including titles, descriptions, and full project paths, from arbitrary private projects across the instance wi…
Affected
GitLab before 19.3.6, 19.4, 19.4.3, 19.5, 19.5.1
Fix
Upgrade GitLab to 19.3.6, 19.4, 19.4.3, 19.5 or 19.5.1 (whichever matches your release line), or later.
Exploitation
No known exploitation

Story map

Story map: GitLabTHE FLAWSTHE FIXCVE-2026-13319Authorisation bypassCVSS 6.5 · EPSS 0%CVE-2026-97229Integer overflow can lead toremote code executionCVSS 10.0 · EPSS 18%CVE-2026-110264Integer overflow can lead toremote code executionCVSS 10.0 · EPSS 1%CVE-2026-93577Integer overflow can lead toremote code executionCVSS 9.9 · EPSS 1%Upgrade GitLab19.3.6 · 19.4 · 19.4.3 · 19.5 ·19.5.1 · 19.2.8or later on your release lineWho is exposedGitLab before 19.2.8, 19.3,19.3.5, 19.4, 19.4.2RED · ACT TODAYGitLabGitLab has remediated an issuein GitLab CE/EE affecting allversions from 19.2 before 19.2.8,19.3 before 19.3.5, and 19.4before 19.4.2 that, under certainconditions, could have allowed anunauthenticated user to…Where it standsNo known exploitation1 outlet covering itHOW IT UNFOLDEDOfficial record on the left, the press on the right, oldest first.22 Oct · BleepingComputerGitLab warns of new max severity code executionvulnerabilityCONNECTS TOSame weaknessAuthorisation bypass (CWE-639)253 other warnings in 30 days →Same productEarlier GitLab warnings39 in the last 90 days →Reported alongsideGitLab Community Edition andEnterprise Edition Path…CVE-2026-85706 · in 1 of the samearticle →
Story map: the flaws, the fix, how it unfolded and what it connects to. Boxes link to the record or article.

At a glance

GitLab: Red, act today. GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD confi…

The flaws

  • CVE-2026-13319: Authorisation bypass (CVSS 6.5 · EPSS 0%)
  • CVE-2026-97229: Integer overflow can lead to remote code execution (CVSS 10.0 · EPSS 18%)
  • CVE-2026-110264: Integer overflow can lead to remote code execution (CVSS 10.0 · EPSS 1%)
  • CVE-2026-93577: Integer overflow can lead to remote code execution (CVSS 9.9 · EPSS 1%)

The fix

Upgrade GitLab: 19.3.6 · 19.4 · 19.4.3 · 19.5 · 19.5.1 · 19.2.8 or later on your release line

Who is exposed: GitLab before 19.2.8, 19.3, 19.3.5, 19.4, 19.4.2

Where it stands

  • No known exploitation
  • 1 outlet covering it

How it unfolded

  1. 22 Oct, BleepingComputer (press): GitLab warns of new max severity code execution vulnerability

Connects to

Why it is Yellow

  • CVSS 6.5 medium

References

Original description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.10 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, could have allowed an authenticated to read milestone metadata, including titles, descriptions, and full project paths, from arbitrary private projects across the instance without any project membership, due to missing authorization checks on a user-supplied project filter parameter in the group milestones API.

Last activity 22 Oct 2026. Patch Forecast updates every hour.