GPU VulnDB

Database/Control plane, storage & DevOps

GitLab EE: developer-role user can bypass admin AI tool governance controls in a governed namespace

CVSS 4.3CVE-2026-129253Control plane, storage & DevOpscurated

Impact

Authorization tokens are not properly bound to the workflow execution they were issued for. As a result, a developer-role user can get around the AI tool governance controls an administrator set on a governed namespace. Operators who rely on those controls to restrict what AI agents may do should treat them as unenforced until patched. The record describes no direct data exposure.

Who can reach it

An authenticated GitLab EE user with Developer role or higher in a governed namespace. Network access to the instance is required.

What to do

Upgrade GitLab EE to 19.3.9, 19.4.8 or 19.5.6. Versions from 19.1 are affected. Upgrading a self-managed instance restarts the GitLab services.

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.