Read the docs

Incorrect authorization in GitLab lets developers bypass AI tool governance

Priority LOW 35CWE-863Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
None · Low · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-863.

Summary

GitLab EE from 19.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 is affected. Due to improper binding of authorization tokens to their intended workflow execution context, an authenticated user with developer-role permissions can bypass admin-configured AI tool governance controls in a governed namespace under certain conditions. The CWE-863 weakness is incorrect authorization, and the attack requires low privileges and no user interaction.

Written with Claude Haiku 5.5 from the sources below · 2026-11-17

Description from the CNA

GitLab has remediated an issue in GitLab EE affecting all versions from 19.1 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain conditions could have allowed an authenticated user with developer-role permissions to bypass admin-configured AI tool governance controls in a governed namespace due to improper binding of authorization tokens to their intended workflow execution context.

Why it matters now

Fix Fixed GitLab (GitLab): 19.3.9, 19.4.8, 19.5.6

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
GitLabGitLab19.1 to before 19.3.9; 19.4 to before 19.4.8; 19.5 to before 19.5.619.3.9, 19.4.8, 19.5.6Patch availableCNA
  • GitLab VendorGitLab Affected 19.1 to before 19.3.9; 19.4 to before 19.4.8; 19.5 to before 19.5.6 Fixed in 19.3.9, 19.4.8, 19.5.6 Patch available CNA

CPE names CNA · 1

CPEVersionsRoleVendor
cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*——GitLab
  • cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:* Versions — — ·GitLab

Remediation

GitLab fixes this in versions 19.3.9, 19.4.8, and 19.5.6 of GitLab EE. Upgrade to one of these fixed versions or later.

Written with Claude Haiku 5.5 from the sources below · 2026-11-17

  • Fix · CNA GitLab (GitLab) Fixed in 19.3.9, 19.4.8, 19.5.6

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    GitLab 19.3.9, 19.4.8, 19.5.6

    36 records Highest priority Priority MEDIUM 9 MEDIUM, 27 LOW

    Other records, highest priority first

    • TI-2026-92431 Cross-site scripting in GitLab Error Tracking pagesPriority MEDIUM 53
    • TI-2026-92429 Cross-site scripting in GitLab wiki pagesPriority MEDIUM 53
    • TI-2026-92420 Incorrect authorization in GitLab exposes protected CI/CD variablesPriority MEDIUM 51

Timeline

  1. 2026-11-17 Threatist record created from CVE-2026-129253
  2. 2026-11-17 Alias added: GHSA-34m6-5973-3qmh

References

  • TI-2026-71508 Integer overflow in GitLab lets unauthenticated users run code KEVCVSS 3.1CRITICAL 10.0
  • TI-2026-58817 Path traversal in GitLab lets unauthenticated users read server files KEVCVSS 3.1CRITICAL 10.0
  • TI-2023-06425 Password reset emails sent to unverified addresses in GitLab KEVCVSS 3.1CRITICAL 10.0
  • TI-2021-05191 Remote command execution in GitLab CE/EE via crafted image files KEVCVSS 3.1CRITICAL 10.0
  • TI-2021-05161 Server-side request forgery in GitLab webhooks KEVCVSS 3.1CRITICAL 9.8
  • TI-2022-02763 Injection in GitLab CVSS 3.1CRITICAL 9.9
See all 1524 →

Sources