Is CVE-2026-5954 exploited in the wild?

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

How severe is CVE-2026-5954?

Medium severity, with a CVSS score of 4.2, published 13 October 2026.

Which products and versions are affected?

GitLab Community Edition 15.1 through 19.2.7, 19.3.0 through 19.3.4, 19.4.0 through 19.4.1; GitLab Enterprise Edition 15.1 through 19.2.7, 19.3.0 through 19.3.4, 19.4.0 through 19.4.1.

Is there a fix for CVE-2026-5954?

Yes: fixed in GitLab CE/EE 19.2.8, 19.3.5, 19.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-5954 attacked?

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

Am I affected by CVE-2026-5954?

Check whether you run GitLab, GitLab Community Edition or GitLab Enterprise Edition 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-5954: GitLab CE/EE improper authorization in package registry

CVE-2026-5954 · Severity: medium · CVSS 4.2 · Published 2026-10-13

GitLab is a web-based DevOps platform used by development teams to manage code repositories and CI/CD pipelines. A flaw in access controls allows users to download package files from public projects they should not be able to access. An attacker could retrieve sensitive artifacts or dependencies without proper authorization.

Technologies: GitLab, GitLab Community Edition, GitLab Enterprise Edition. Vendors: GitLab.

Quick answers

Is CVE-2026-5954 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-5954 being exploited in the wild.
How severe is CVE-2026-5954?: Medium severity, with a CVSS score of 4.2, published 13 October 2026.
Which products and versions are affected?: GitLab Community Edition 15.1 through 19.2.7, 19.3.0 through 19.3.4, 19.4.0 through 19.4.1; GitLab Enterprise Edition 15.1 through 19.2.7, 19.3.0 through 19.3.4, 19.4.0 through 19.4.1.
Is there a fix for CVE-2026-5954?: Yes: fixed in GitLab CE/EE 19.2.8, 19.3.5, 19.4.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-5954 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-5954?: Check whether you run GitLab, GitLab Community Edition or GitLab Enterprise Edition 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.2.8, 19.3.5, 19.4.2

Technical details

An improper authorization check in the package registry allows authenticated or unauthenticated users under certain conditions to download package files from public projects via the network. The vulnerability stems from insufficient access control validation. Fixes are available in GitLab CE/EE 19.2.8, 19.3.5, and 19.4.2.

Affected products

GitLab GitLab Community Edition 15.1 through 19.2.7, 19.3.0 through 19.3.4, 19.4.0 through 19.4.1
GitLab GitLab Enterprise Edition 15.1 through 19.2.7, 19.3.0 through 19.3.4, 19.4.0 through 19.4.1

Timeline

2026-10-13: disclosed
2026-10-12: patched: Versions 19.2.8, 19.3.5, 19.4.2 released

References

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