CVE-2026-112378: GitLab EE use of less trusted source in AI Gateway feature enablement header
GitLab EE trusted the AI Gateway feature enablement header more than it should. Billing eligibility checks lacked enough server-side validation, so an authenticated user could use paid AI features without a valid subscription. GitLab EE 17.8 up to 19.3.6, 19.4 before 19.4.3 and 19.5 before 19.5.1 are affected. Upgrade to 19.3.6, 19.4.3 or 19.5.1.
Published Oct 21, 2026 · Analysis Oct 22, 2026
What an attacker can do
The weakness is CWE-348, use of a less trusted source. GitLab's bulletin titles it "Use of Less Trusted Source issue in AI Gateway feature enablement header". It describes insufficient server-side validation in billing eligibility checks, which lets an authenticated user reach paid AI features that their subscription does not cover.
The impact is on integrity of licensing, not on data. The CVSS 3.1 vector (4.3, medium) shows network access, low privileges, no user interaction and a low integrity effect, with no confidentiality or availability effect. In practice the person at risk is the instance owner: users on an EE instance without the right add-on could consume AI features that are billed, which means cost and licence compliance problems. GitLab does not say which header or which features are involved, and it does not say the flaw allows access to other users' data.
The attacker needs a normal account on the instance. The bulletin reports no exploitation.
Who is affected
GitLab EE only: all versions from 17.8 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1. The GitLab CE package is not listed in the affected range for this issue even though the patch release covers both editions. Check the version in the Admin Area, on the /help page, or on the host:
dpkg -l gitlab-eeUse rpm -q gitlab-ee on RPM-based systems.
How to fix it
Upgrade to GitLab 19.5.1, 19.4.3 or 19.3.6, whichever matches your release line. They were released on October 21, 2026. GitLab lists no workaround for this issue and recommends upgrading self-managed installations as soon as possible. GitLab.com already runs the fix.
How to tell if you were hit
The bulletin gives no log signature. Compare AI feature usage (for example Duo requests) against the users and groups that hold the matching subscription seats. Look for accounts without a seat that show AI activity in the audit events and in your billing or usage reports for the affected period.
Original advisory
From the National Vulnerability Database. This product uses the NVD API but is not endorsed or certified by the NVD.
Under certain conditions, an authenticated user could have accessed paid AI features without a valid subscription due to insufficient server-side validation in billing eligibility checks. Impacted versions: GitLab EE all versions from 17.8 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1. Fixed in GitLab CE/EE 19.5.1, 19.4.3 and 19.3.6, released October 21, 2026.
Questions
- Which GitLab versions fix CVE-2026-112378?
19.5.1, 19.4.3 and 19.3.6, released October 21, 2026. The affected range starts at 17.8.
- Does this expose my repositories or user data?
Nothing in the bulletin says so. The flaw is about billing eligibility: an authenticated user reaching paid AI features without a valid subscription. The CVSS vector shows low integrity impact only.
- Does it affect GitLab CE?
The advisory lists GitLab EE as affected. The fixes ship in the same patch release for both editions.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
Coverage on the Beam blog
More GitLab vulnerabilities
All GitLab entriesCVE-2026-103515
GitLab EE improper access control in group Duo admin-lock enforcement for Amazon Q settings
low2.7Oct 21, 2026CVE-2026-105711
GitLab CE/EE use of cache containing sensitive information in merge request title rendering
low3.5Oct 21, 2026CVE-2026-105777
GitLab CE/EE internal credential exposure in internal response headers
medium4.3Oct 21, 2026CVE-2026-110264
GitLab CE/EE integer overflow in regular expression compiler allows unauthenticated remote code execution
critical10.0Oct 21, 2026CVE-2026-112212
GitLab CE/EE cache poisoning in OAuth/OIDC discovery endpoints
high7.5Oct 21, 2026CVE-2026-112326
GitLab EE improper cleanup on thrown exception in security findings
low3.1Oct 21, 2026
