GPU VulnDB

Database/Control plane, storage & DevOps

GitLab CE/EE: missing CSRF protection lets an unauthenticated attacker run GraphQL mutations as a logged-in user

CVSS 8.1CVE-2026-4922Control plane, storage & DevOpscurated

Impact

The CSRF protection on the GraphQL endpoint is incomplete. An unauthenticated attacker who gets a logged-in GitLab user to load attacker-controlled content can run GraphQL mutations with that user's permissions. The record does not limit which mutations are reachable. In a GPU shop the self-hosted GitLab holds pipeline definitions, CI variables and runner registration, so a mutation fired from a maintainer's or admin's session could change what runs on build and GPU CI nodes. GitLab scores it high on confidentiality and integrity.

Who can reach it

A remote attacker with no GitLab account, who needs a victim with an active GitLab session to interact with attacker-controlled content (UI:R). The attacker gets whatever permissions the victim has.

What to do

Upgrade GitLab to 18.9.6, 18.10.4 or 18.11.1, depending on your branch. All versions from 17.0 are affected. This is an application upgrade and service restart on the GitLab host, with no fleet maintenance window. Until it is patched, admins and maintainers should not browse untrusted sites while logged in to GitLab.

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.