Is CVE-2026-112212 exploited in the wild?

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

How severe is CVE-2026-112212?

High severity, with a CVSS score of 7.5, published 22 October 2026.

Which products and versions are affected?

GitLab Community Edition 18.3 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1; GitLab Enterprise Edition 18.3 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1.

Is there a fix for CVE-2026-112212?

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

How is CVE-2026-112212 attacked?

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

Am I affected by CVE-2026-112212?

Check whether you run 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-112212: GitLab cache poisoning in OAuth/OIDC discovery

CVE-2026-112212 · Severity: high · CVSS 7.5 · Published 2026-10-22

GitLab is a collaboration platform that organizations use for version control and CI/CD pipelines. An unauthenticated attacker could poison the cached OAuth/OIDC discovery document to redirect authentication flows to an attacker-controlled server, potentially enabling account takeover or credential theft from users attempting to log in.

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

Quick answers

Is CVE-2026-112212 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-112212 being exploited in the wild.
How severe is CVE-2026-112212?: High severity, with a CVSS score of 7.5, published 22 October 2026.
Which products and versions are affected?: GitLab Community Edition 18.3 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1; GitLab Enterprise Edition 18.3 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1.
Is there a fix for CVE-2026-112212?: Yes: fixed in GitLab CE/EE 19.3.6, 19.4.3, 19.5.1 (also backported to 18.11.13, 19.0.10, 19.1.9, 19.2.9). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-112212 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-112212?: Check whether you run 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.3.6, 19.4.3, 19.5.1 (also backported to 18.11.13, 19.0.10, 19.1.9, 19.2.9)

Technical details

The vulnerability is a cache poisoning issue in OAuth/OIDC discovery endpoints affecting GitLab CE and EE. An unauthenticated attacker can exploit improper trust of user-supplied values when constructing endpoint URLs in cached discovery responses to redirect authentication flows. The attack requires user interaction and affects a shared cache, enabling phishing or credential interception attacks against users authenticating via OAuth/OIDC.

Affected products

GitLab GitLab Community Edition 18.3 before 19.3.6, 19.4 before 19.4.3, 19.5 before 19.5.1
GitLab GitLab Enterprise Edition 18.3 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.