Is CVE-2026-112378 exploited in the wild?

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

How severe is CVE-2026-112378?

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

Which products and versions are affected?

GitLab Enterprise Edition 17.8 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1.

Is there a fix for CVE-2026-112378?

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

How is CVE-2026-112378 attacked?

It is attacked over the network.

Am I affected by CVE-2026-112378?

Check whether you run 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-112378: GitLab Enterprise Edition authorization bypass in billing validation

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

GitLab Enterprise Edition, which provides source code management and CI/CD capabilities for development teams, has a flaw in its billing system that allows authenticated users to access premium AI features without paying for them. An attacker with a valid account could gain access to paid AI capabilities that should be restricted to subscribers, effectively obtaining unauthorized functionality.

Technologies: GitLab Enterprise Edition. Vendors: GitLab.

Quick answers

Is CVE-2026-112378 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-112378 being exploited in the wild.
How severe is CVE-2026-112378?: Medium severity, with a CVSS score of 4.3, published 22 October 2026.
Which products and versions are affected?: GitLab Enterprise Edition 17.8 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1.
Is there a fix for CVE-2026-112378?: Yes: fixed in GitLab EE 19.3.6, 19.4.3, 19.5.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-112378 attacked?: It is attacked over the network.
Am I affected by CVE-2026-112378?: Check whether you run 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 EE 19.3.6, 19.4.3, 19.5.1

Technical details

An authenticated user can bypass billing eligibility checks due to insufficient server-side validation, allowing access to paid AI features without a valid subscription. The vulnerability requires authentication and affects versions 17.8 through 19.5.0. A fix is available in GitLab EE 19.3.6, 19.4.3, and 19.5.1.

Affected products

GitLab Enterprise Edition 17.8 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1

Timeline

2026-10-22: disclosed
2026-10-21: patched

References

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