GPU VulnDB

Database/Control plane, storage & DevOps

GitLab CE/EE: unauthenticated poisoning of the cached OIDC discovery document redirects auth flows

CVSS 7.5CVE-2026-112212Control plane, storage & DevOpscurated

Impact

GitLab constructed endpoint URLs in cached OAuth/OIDC discovery responses while improperly trusting user-supplied values, so under some conditions an unauthenticated requester could poison the shared cache and point certain authentication flows at a server they control. Because the poisoned entry lives in a shared cache, the effect is not limited to the attacker's own session - the CVSS vector records a scope change. For a GPU operator this is a CI/CD and identity problem rather than a node problem: GitLab typically holds the pipelines that build and ship training and serving images and the runner credentials that reach the fleet, so redirected auth flows are a route to the supply chain for the cluster.

Who can reach it

Unauthenticated requests to a reachable GitLab instance, with user interaction required to complete the redirected flow per the vendor's vector (AV:N/AC:H/PR:N/UI:R). Any GitLab exposed to users or to the internet is in range.

What to do

Upgrade to GitLab 19.3.6, 19.4.3 or 19.5.1 (affected: all versions from 18.3 before those). For a self-managed instance that is a package upgrade and a service restart - the usual GitLab maintenance window, no node drain. Clear or let expire any poisoned discovery cache entries after upgrading. GitLab.com is already patched by the vendor.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.