CVE-2026-104661 GitLab CVE debrief

Who should care

GitLab EE administrators and security teams should assess exposure and apply patches to remediate the vulnerability. They should also review official advisories, verify exposure in their deployments, and monitor for suspicious compliance pipeline activity. Additionally, they should prioritize verifying exposure, applying patches, and monitoring for suspicious activity to prevent potential privilege escalation.

Why it matters

The CVE-2026-104661 vulnerability in GitLab EE could allow an authenticated user to configure and execute a specially crafted compliance pipeline across group projects due to improper privilege assignment. Defenders should prioritize verifying exposure, applying patches, and monitoring for suspicious activity.

• Verify exposure in GitLab EE deployments to prevent potential privilege escalation
• Apply patches to remediate the improper privilege assignment vulnerability and prevent exploitation
• Monitor for suspicious compliance pipeline activity to detect potential malicious behavior

Technical summary

The vulnerability affects GitLab EE versions from 17.0 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2. An authenticated user with a custom role holding compliance framework administration permissions could configure and execute a specially crafted compliance pipeline across group projects due to improper privilege assignment. This could allow an authenticated user to configure and execute a specially crafted compliance pipeline across group projects due to improper privilege assignment. Defenders should prioritize verifying exposure in GitLab EE deployments and applying patches to remediate the improper privilege assignment vulnerability.

Defensive priority

Defenders should prioritize verifying exposure in GitLab EE deployments and applying patches to remediate the improper privilege assignment vulnerability.

Recommended defensive actions

• Verify exposure in GitLab EE deployments
• Apply patches to remediate the improper privilege assignment vulnerability
• Monitor for suspicious compliance pipeline activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the affected GitLab EE versions and the nature of the improper privilege assignment vulnerability. Defenders should verify exposure in their GitLab EE deployments, review official advisories, and apply patches to remediate the vulnerability. The vulnerability affects GitLab EE versions from 17.0 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2. An authenticated user with a custom role holding compliance framework administration permissions could configure and execute a The CV

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.