GitLab EE: missing namespace validation lets a user apply compliance frameworks from namespaces they cannot access

Impact

On self-managed GitLab EE, an authenticated user could attach a compliance framework belonging to a namespace they have no rights to onto a project they control, because the assignment path did not validate namespace membership. The consequence established by the record is integrity of compliance metadata: the framework applied to a project, and therefore the policy set and audit posture reported for it, can be made to disagree with what the owning namespace intended. For a GPU shop that uses GitLab as the CI/CD path building and signing the container images the fleet runs, compliance frameworks are often the hook that decides which pipeline policies and approval rules apply, so a wrong framework can quietly weaken or confuse that gating. No repository access, code execution or credential disclosure is claimed - this is a scoped authorization defect, not a takeover.

Who can reach it

Any authenticated user on a self-managed GitLab EE instance who owns or maintains a project and can reach the web UI or API. No administrator rights and no membership in the victim namespace are needed.

What to do

Upgrade to GitLab 19.1.7, 19.2.5 or 19.3.1 depending on your stream (all versions from 18.3 are affected). This is an application upgrade and reconfigure on the GitLab host or a rolling restart of the GitLab pods - GPU nodes are untouched and no maintenance window on the fleet is needed. GitLab.com is not affected; the issue is specific to self-managed instances.

References

Related entries

• LibreNMS: reflected XSS in the Proxmox view runs script in a logged-in monitoring user's sessionCVE-2026-45694 · LibreNMS (Proxmox application view, instance and vmid parameters)Medium
• Strimzi: partial Entity Operator deployments still get both operators' RBAC, over-granting the SACVE-2026-55226 · Strimzi Kafka Operator (Entity Operator ServiceAccount RBAC)Medium
• Jenkins Stapler: form binding writes public static fields, applying changes instance-wideCVE-2026-84654 · Jenkins Stapler (form data binding to public static fields)Medium
• Jenkins Pipeline: Build Step Plugin: downstream builds cancelled without Item/Cancel permission checkCVE-2026-84660 · Jenkins Pipeline: Build Step Plugin (build and waitForBuild step cancellation)Medium
• Jenkins Pipeline: Groovy Libraries plugin: CSRF lets an unauthenticated attacker delete library cachesCVE-2026-84663 · Jenkins Pipeline: Groovy Libraries Plugin (shared library cache deletion endpoint)Medium
• Jenkins GitLab plugin: global connection URL can be overwritten, sending admin API tokens to an attackerCVE-2026-84664 · Jenkins GitLab Plugin (global connection configuration via Stapler data binding)Medium