Is CVE-2026-13319 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-13319 being exploited in the wild.

How severe is CVE-2026-13319?

Medium severity, with a CVSS score of 4.3, published 22 October 2026.

Which products and versions are affected?

GitLab CE 15.10 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1; GitLab EE 15.10 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1.

Is there a fix for CVE-2026-13319?

Yes: fixed in GitLab CE/EE 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, 18.11.13. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-13319 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-13319?

Check whether you run GitLab CE or GitLab EE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-13319: GitLab authorization bypass in group milestones API

CVE-2026-13319 · Severity: medium · CVSS 4.3 · Published 2026-10-22

GitLab, a web-based platform for managing software development projects, contains a flaw in its group milestones API that allows authenticated users to read sensitive metadata from private projects they don't have access to. An attacker with any GitLab account could discover project names, milestone titles, descriptions, and internal paths from confidential projects across the entire instance without permission.

Technologies: GitLab CE, GitLab EE. Vendors: GitLab.

Quick answers

Is CVE-2026-13319 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-13319 being exploited in the wild.
How severe is CVE-2026-13319?: Medium severity, with a CVSS score of 4.3, published 22 October 2026.
Which products and versions are affected?: GitLab CE 15.10 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1; GitLab EE 15.10 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1.
Is there a fix for CVE-2026-13319?: Yes: fixed in GitLab CE/EE 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, 18.11.13. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-13319 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-13319?: Check whether you run GitLab CE or GitLab EE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: GitLab CE/EE 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, 18.11.13

Technical details

The group milestones API endpoint lacks proper authorization checks on a user-supplied project filter parameter, allowing an authenticated attacker to enumerate and retrieve milestone metadata from arbitrary private projects. The vulnerability requires authentication but no project membership. A fix is available in versions 19.5.1, 19.4.3, 19.3.6, and earlier patch releases of affected branches.

Affected products

GitLab GitLab CE 15.10 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1
GitLab GitLab EE 15.10 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1

Timeline

2026-10-21: advisory
2026-10-21: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.