GitLab

Help us learn about your current experience with the documentation. Take the survey.

On September 10, 2026, we released versions 19.3.2, 19.2.6, 19.1.8 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, please visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here. For security fixes, the issues detailing each vulnerability are made public on our issue tracker 90 days after the release in which they were patched. We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post.

Recommended Action

We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible. When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, it means all types are affected.

Security fixes

Table of security fixes

TitleSeverity Path Traversal issue in repository commits API impacts GitLab CE/EECritical Insecure Deserialization issue in GraphQL subscription serializer impacts GitLab EECritical Buffer Overflow issue in Unicode conversion wrapper impacts GitLab EEHigh Scheduled Pipeline Execution Policy test allows Developers to access protected CI/CD variablesHigh Cross-site Scripting issue in Markdown JSON table renderer impacts GitLab CE/EEHigh Incorrect Authorization issue in CI/CD environment variable scope matcher impacts GitLab CE/EEHigh Denial of Service issue in GraphQL complexity limiter impacts GitLab CE/EEHigh Denial of Service issue in GraphQL complexity limiter impacts GitLab CE/EEHigh Race Condition issue in Merge Request Pipelines impacts GitLab CE/EEMedium Improper Authentication issue in SAML SSO sign-in restriction enforcement impacts GitLab CE/EEMedium Insufficiently Protected Credentials issue in Workhorse senddata emitters impacts GitLab CE/EEMedium Cross-site Scripting issue in Content Editor impacts GitLab CE/EEMedium Access Control Implementation issue in protected environment approval rules impacts GitLab EEMedium Authorization Bypass issue in protected environment approval rules impacts GitLab EEMedium Missing Authorization issue in Generic Package Registry impacts GitLab CE/EEMedium Improper Input Validation issue in Namespace Transfer impacts GitLab CE/EEMedium Missing Authorization issue in Compliance Framework management impacts GitLab EEMedium Improper Input Validation issue in Terraform State API impacts GitLab CE/EELow

CVE-2026-85706 - Path Traversal issue in repository commits API impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, an unauthenticated user could have read arbitrary files from the GitLab server due to improper path confinement and missing authentication enforcement in the repository commits API. Impacted Versions: GitLab CE/EE: all versions from 18.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2CVSS 10.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N) Thanks s3ntago for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-87719 - Insecure Deserialization issue in GraphQL subscription serializer impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, could allow an authenticated user with Duo Chat access to obtain Advanced Search instance configurations and sensitive credentials using a specially crafted GraphQL subscription argument to bypass serialization and perform server object lookup. Impacted Versions: GitLab EE: all versions from 18.3 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2CVSS 9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) Thanks kyyblin for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-88765 - Buffer Overflow issue in Unicode conversion wrapper impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, could allow an authenticated user to achieve remote code execution by importing a specially crafted Git project export to overflow the Unicode conversion buffer used in Advanced Search indexing. Impacted Versions: GitLab EE: all versions from 12.3 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2CVSS 8.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H) Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-79708 - Scheduled Pipeline Execution Policy test allows Developers to access protected CI/CD variables

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user with developer permissions to execute a policy test pipeline on projects within their group and access protected CI/CD variables restricted to higher-privileged roles due to insufficient scope validation. Impacted Versions: GitLab EE: all versions from 19.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2CVSS 8.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N) Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-78252 - Cross-site Scripting issue in Markdown JSON table renderer impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, an authenticated user could have induced a targeted user to perform unintended state-changing HTTP requests due to improper sanitization of user-controlled data in the Markdown JSON table renderer. Impacted Versions: GitLab CE/EE: all versions from 15.3 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2CVSS 8.2 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:L) Thanks a_m_a_m for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-13210 - Incorrect Authorization issue in CI/CD environment variable scope matcher impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user to access CI/CD variables outside their intended environment scope due to improper input validation in the environment scope pattern matcher. Impacted Versions: GitLab CE/EE: all versions from 15.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2CVSS 7.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N) Thanks nwicks for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2025-14871 - Denial of Service issue in GraphQL complexity limiter impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an unauthenticated user to cause denial of service due to improper resource allocation limits in the GraphQL complexity calculation logic. Impacted Versions: GitLab CE/EE: all versions from 18.4.6 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Thanks hunter0xp7 for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-1168 - Denial of Service issue in GraphQL complexity limiter impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an unauthenticated user to cause denial of service due to improper resource allocation limits in the GraphQL complexity calculation logic. Impacted Versions: GitLab CE/EE: all versions from 18.4.6 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2024-11222 - Race Condition issue in Merge Request Pipelines impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed a developer user to perform actions in the context of another user’s merge request commit due to a race condition issue in pipeline creation. Impacted Versions: GitLab CE/EE: all versions from 13.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2CVSS 6.4 (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N) Thanks xorz for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-12910 - Improper Authentication issue in SAML SSO sign-in restriction enforcement impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user to bypass SAML SSO sign-in restrictions and authenticate without SSO due to missing authentication enforcement checks. Impacted Versions: GitLab CE/EE: all versions from 18.6 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2CVSS 5.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) Thanks theluci for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-82837 - Insufficiently Protected Credentials issue in Workhorse senddata emitters impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user to access sensitive credentials and tokens without transiting the expected proxy due to improper authorization checks on internal data emission endpoints. Impacted Versions: GitLab CE/EE: all versions from 10.1.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) Thanks 0xoroot for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-19619 - Cross-site Scripting issue in Content Editor impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary JavaScript in the context of a targeted user’s session due to improper sanitization of pasted HTML content in the Content Editor. Impacted Versions: GitLab CE/EE: all versions from 19.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2CVSS 4.7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N) Thanks lucvs for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-86341 - Access Control Implementation issue in protected environment approval rules impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, an authenticated user with Owner or Maintainer permissions could have silently disabled protected environment deployment approval requirements, allowing unapproved deployments to reach production due to improper access control checks performed after the protected resource was modified. Impacted Versions: GitLab EE: all versions from 17.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2CVSS 4.4 (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N) This vulnerability has been discovered internally by GitLab team member Peter Arts.

CVE-2026-86340 - Authorization Bypass issue in protected environment approval rules impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, could allow an authenticated user to bypass required deployment approvals for protected environments by deleting the sole approver group or user account. Impacted Versions: GitLab EE: all versions from 17.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2CVSS 4.4 (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:N) …

Help us learn about your current experience with the documentation. Take the survey.

On August 26, 2026, we released versions 19.3.1, 19.2.5, 19.1.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, please visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here. For security fixes, the issues detailing each vulnerability are made public on our issue tracker 90 days after the release in which they were patched. We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post.

Recommended Action

We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible. When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, it means all types are affected.

Security fixes

Table of security fixes

TitleSeverity Inclusion of Functionality from Untrusted Control Sphere issue in Duo Claude AI agent impacts GitLab EEHigh Denial of Service issue in import pipeline impacts GitLab CE/EEMedium Denial of Service issue in SCIM API impacts GitLab EEMedium Improper Access Control issue in protected environments impacts GitLab EEMedium Authorization Bypass issue in compliance framework assignment impacts GitLab EEMedium Improper Handling of Untrusted Data issue in Pipeline Execution Policies impacts GitLab EEMedium Improper Authorization issue in merge request approval rules reset impacts GitLab EELow

CVE-2026-18252 - Inclusion of Functionality from Untrusted Control Sphere issue in Duo Claude AI agent impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, an authenticated user with developer-role permissions could have executed arbitrary commands in a CI context, due to the Claude agent processing configuration from a user-controlled source. Impacted Versions: GitLab EE: all versions from 18.9 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1CVSS 7.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N) Thanks thwin_htet for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-77801 - Denial of Service issue in import pipeline impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, an authenticated user could have caused denial of service affecting background job processing, due to missing object count limits. Impacted Versions: GitLab CE/EE: all versions from 12.8 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) Thanks Tran Ba Quang for reporting this vulnerability

CVE-2025-10903 - Denial of Service issue in SCIM API impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, an authenticated user could have caused denial of service, due to an unbounded loop triggered by specially crafted input in the SCIM user provisioning feature. Impacted Versions: GitLab EE: all versions from 11.10 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) Thanks rafabd1 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-3035 - Improper Access Control issue in protected environments impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, an authenticated user with project Maintainer permissions could have accessed the terminal of a protected environment they were not authorized to use due to improper authorization checks. Impacted Versions: GitLab EE: all versions from 11.3 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1CVSS 5.5 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N) Thanks go7f0 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-4398 - Authorization Bypass issue in compliance framework assignment impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, an authenticated user could have assigned compliance frameworks from namespaces they were not authorized to access to their own project, due to missing namespace validation on self-managed instances. Impacted Versions: GitLab EE: all versions from 18.3 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1CVSS 5.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) Thanks bountyyfi for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-15387 - Improper Handling of Untrusted Data issue in Pipeline Execution Policies impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, an authenticated user with developer-role permissions could have influenced the execution environment of Pipeline Execution Policy enforcement jobs, due to improper handling of job dependencies. Impacted Versions: GitLab EE: all versions from 19.1 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) Thanks 3nvz for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-7487 - Improper Authorization issue in merge request approval rules reset impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, an authenticated user with reporter-role permissions who authored a merge request could have reset merge request approval rules due to improper authorization checks. Impacted Versions: GitLab EE: all versions from 13.1 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1CVSS 3.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N) Thanks rogerace for reporting this vulnerability through our HackerOne bug bounty program

Bug fixes

19.3.1

• Backport ‘Provision inherited foundational flows without user elevation’ to 19-3-stable-ee
• Backport 19.3 release notes to 19-3-stable-ee
• Backport of “Fix MCP OAuth Protected Resource Metadata resource field to return string instead of array”
• Backport of “Gate tracked ref filter on advanced vulnerability management”
• Backport of ‘Reorder deployments bigint cleanup so the FK sorts first’
• Backport of 19.3 release note correction - redesigned agentic chat UI release post

19.2.5

• Backport of ‘Fix broken master by making tests date-independent’
• Backport of: Install glab from official GitLab releases instead of third-party mirror
• Backport of ‘Add import_jobs_concurrency_limit to application settings’
• Backport of Fix infinite loop parsing errored SARIF security reports (19.2)
• Backport of ‘Preserve email reply content after lone bullet lines’
• Release post backport: Add dedicated-hosted-ai-gateway release note to 19-2-stable-ee
• Backport: Add dedicated_self_hosted_models.md to 19.2
• Backport of “Fix MCP OAuth Protected Resource Metadata resource field to return string instead of array”
• Backport of ‘Fix order-dependent epic import gap’
• Backport of Fix drop_ai_* tables migrations
• Backport of “Send Duo availability params only when changed” (19.2)
• [19.2] Backport fixes for Mattermost deprecation
• Bump gitlab-omnibus-builder version to 5.63.1

19.1.7

• Backport of: Install glab from official GitLab releases instead of third-party mirror
• Backport of ‘Add import_jobs_concurrency_limit to application settings’
• Backport of Fix infinite loop parsing errored SARIF security reports (19.1)
• Backport of ‘Preserve email reply content after lone bullet lines’
• Backport of ‘Avoid unbounded preload in any_merge_request rules sync’
• Backport of “Send Duo availability params only when changed” (19.1)
• [19.1] Backport fixes for Mattermost deprecation

Important notes on upgrading

This patch includes database migrations that may impact your upgrade process.

Impact on your installation:

• Single-node instances: This patch will cause downtime during the upgrade as migrations must complete before GitLab can start.
• Multi-node instances: With proper zero-downtime upgrade procedures, this patch can be applied without downtime.

Regular migrations

The following versions include regular migrations that run during the upgrade process:

• 19.3.1
• 19.2.5
• 19.1.7

Post-deploy migrations

The following versions include post-deploy migrations that can run after the upgrade:

• 19.3.1
• 19.2.5 To learn more about the impact of upgrades on your installation, see:
• Zero-downtime upgrades for multi-node deployments
• Standard upgrades for single-node installations

Updating

To update GitLab, see the Update page. To update GitLab Runner, see the Updating the Runner page.

Receive Patch Notifications

To receive patch blog notifications delivered to your inbox, visit our contact us page. To receive release notifications via RSS, subscribe to our patch release RSS feed or our RSS feed for all releases.

Help us learn about your current experience with the documentation. Take the survey.

On August 20, 2026, GitLab 19.3 was released with the following features. We are excited to recognize gkepas as this month’s Notable Contributor! Giannis has made sustained contributions across the GitLab codebase, the contributor platform, client-go, the Terraform provider, and GitLab Orbit. He is also an active translator and a member of the GitLab Community Discord.

Primary features

Flow Creator foundational agent

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue You can now use the Flow Creator, a purpose-built foundational agent in the AI Catalog, to create custom flows for the GitLab Duo Agent Platform through a plain-language conversation. With the Flow Creator, you describe what you want the flow to do, and the agent produces a complete, runnable flow YAML you can register and use immediately. The agent can also help you debug existing flows and explain framework concepts.

Agentic Core

Resolve merge conflicts with GitLab Duo is generally available

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue In previous versions of GitLab, you had to resolve merge conflicts manually in the GitLab UI or from the command line, even for straightforward cases. Now you can ask GitLab Duo to resolve conflicts for you. Start conflict resolution from the merge widget or the Resolve conflicts page. GitLab Duo analyzes the conflicts, edits the files and commits the resolution to the source branch, and then posts a summary comment on the merge request describing what changed.

Resolve review discussions with GitLab Duo is generally available

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue In previous versions of GitLab, to resolve a code review comment, you had to switch to your editor, implement the fix, commit and push the change, and then manually close the thread. Now you can select Resolve with GitLab Duo and GitLab Duo will address the review discussion for you. GitLab Duo reads the comment and the surrounding code, makes the requested change on the source branch, replies to the discussion with a summary of what changed, and then resolves the thread. If the change does not address the comment correctly, you or the reviewer can reopen the thread.

GitLab Duo CLI plugins and marketplaces (Experiment)

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue GitLab Duo CLI now supports plugins and plugin marketplaces as an experiment, introduced in GitLab Duo CLI 9.10.0. A plugin bundles Agent Skills, custom slash commands, and Model Context Protocol (MCP) servers into a single directory. A marketplace is a catalog of available plugins, hosted in a Git repository or a local directory. GitLab Duo CLI automatically registers the official gitlab-duo-plugins marketplace the first time you use plugins. The marketplace includes three skills for common GitLab workflows:
• mr-review: Reviews a merge request and posts comments.
• stack-changes: Splits a large local change into a stacked merge request chain.
• create-issue: Drafts a GitLab issue from a natural-language description. To install one of the skills, run glab duo cli plugin install @gitlab-duo-plugins or duo plugin install @gitlab-duo-plugins, based on your setup. For compatibility with the existing community plugin ecosystem, GitLab Duo CLI also reads .claude-plugin/marketplace.json files, so existing Claude Code plugin marketplaces work with GitLab Duo CLI without modification.

New GitLab Duo Agentic Chat UI in VS Code (Beta)

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue The GitLab Duo Agentic Chat interface in the GitLab for VS Code extension has a redesigned UI, now available as a beta. The new interface is a rebuilt version of the existing Agentic Chat panel, with the same underlying capabilities: AI models, agents, slash commands, and tool approvals. The redesigned UI is available in GitLab 19.3 with GitLab for VS Code extension 6.87.0 and later. To use the new UI, turn on beta and experimental features for your top-level group or instance, then reload the extension. You can switch between the new and classic UI at any time from the panel. The beta is available for VS Code only.

New MCP tools for reading and searching merge requests

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation · Related Issue You can now use get_merge_request to retrieve a merge request along with its diffs, commits, notes, pipelines, or discussions in a single call, so your AI agent no longer has to chain multiple requests to get the full picture of an MR. You can also use the new list_merge_requests tool to search and filter merge requests by author, assignee, reviewer, state, labels, or free-text query, making it easy to find exactly the MRs you care about without leaving your workflow.

Pre-register MCP OAuth applications

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue Previously, the mcp scope was hidden from the OAuth applications form in the Admin area, so you couldn’t pre-register an OAuth application for your MCP clients without using Dynamic Client Registration (DCR). Now you can create a shared OAuth application with the mcp scope directly from the Admin area, giving your users a stable client ID to reuse and helping you avoid DCR rate limits on shared networks.

See which user authorized each MCP OAuth application

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation · Related Issue Previously, when MCP clients connected to GitLab using OAuth Dynamic Client Registration (DCR), all dynamically-registered OAuth applications appeared in the Admin Area with only a generic client name, making it impossible to tell which user authorized a given application. Now, when you approve an MCP OAuth connection, your username is automatically appended to the application name — for example, [Unverified Dynamic Application] kiro — authorized by @username. You can quickly identify which user is behind each dynamic OAuth application directly from the Admin Area, without any additional configuration.

View agent task plan in session detail sidebar

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue Previously, when you opened a session detail page, you had to manually expand individual activity log entries to find the agent’s current task list. Now, the session detail sidebar shows the agent’s latest plan automatically. You can view each task and its status, and a progress summary like “2 of 5 completed.” You can track what the agent is working on and how far along it is without digging through the activity log.

Devstral 2 deprecated for GitLab Duo Agent Platform Self-Hosted

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Links: Documentation · Related Issue Mistral has deprecated the Devstral 2 model, and GitLab has deprecated Devstral 2 for GitLab Duo Agent Platform Self-Hosted. Mistral Medium 3.5 is a supported alternative available from Mistral.

Support for Amazon Bedrock Mantle (Beta)

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Links: Documentation · Related Issue If you use GitLab Self-Managed with self-hosted models, you can now use Amazon Bedrock Mantle as a supported provider. Mantle is an OpenAI-compatible inference engine for Amazon Bedrock, so you can use familiar OpenAI SDKs and integrations with Bedrock models. This feature is in beta.

Unified DevOps and Security

Enforce merge trains

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation · Related Issue In previous versions of GitLab, you couldn’t stop merges from bypassing the train. Both the option to merge immediately and the REST API could skip merge train protections without restriction. For teams running high-velocity monorepos, a single merge that skips the train can cancel and restart every in-progress pipeline, multiplying CI costs and straining infrastructure. Now you can enforce merge train usage across the UI and API with a single project-level setting, preventing bypasses that cancel and restart in-progress pipelines. Owners and Administrators can still override the setting when needed.

GitLab Secret Scanning for Source Code (Beta)

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed
• Links: Documentation · Related Issue GitLab Secret Scanning for Source Code is now in beta, powered by a new GitLab-built scan engine. Unlike the default analyzer, which detects only known secret patterns, this analyzer also detects passwords and other unstructured secrets that fall outside standard ruleset coverage. It also uses multiple heuristic techniques to reduce false positives. The new analyzer replaces the default analyzer in the same secret_detection job, matching existing vulnerability findings instead of creating duplicates. To get started, see turn on the analyzer. During beta, only high-confidence findings are reported. We welcome any feedback you have in issue 609578.

Secret detection scans commit history on default branch pushes

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation · Related Issue Secret detection on the default branch now scans all commit diffs in a push when a prior commit reference is available, rather than scanning only the latest directory contents. This change closes a gap where secrets introduced and removed within the same push went undetected. The behavior now aligns with how secret detection works on merge requests and feature branches. This scanning catches secrets that briefly existed in your repository history even if removed before the pipeline completes. Security teams can now identify secrets that were ever committed, not just those present at HEAD. For more information, see pipeline secret detection coverage.

Disable OAuth Dynamic Client Registration for MCP

• Tier: Free, Premium, Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue Previously, MCP clients and AI tools could automatically register OAuth applications on your instance through Dynamic Client Registration (DCR), which you couldn’t turn off. This made it difficult for administrators on GitLab Self-Managed and GitLab Dedicated instances to control which OAuth clients could connect. Now you can disable DCR entirely using the application settings API, giving you full control over which OAuth clients can access your instance. When DCR is disabled, clients must use a pre-registered OAuth application instead of registering automatically.

SPDX license expressions in CycloneDX SBOMs brought to GitLab

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue GitLab 19.3 adds support for Software Package Data Exchange (SPDX) license expressions in CycloneDX Software Bill of Materials (SBOM) files you bring to GitLab. Previously, components with composite or custom licenses defined using SPDX expression syntax would appear as unknown. …

Help us learn about your current experience with the documentation. Take the survey.

On August 17, 2026, we released versions 19.2.4, 19.1.6, 19.0.8, 18.11.11 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com and GitLab Dedicated are already running the patched version. GitLab.com and GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, please visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here. For security fixes, the issues detailing each vulnerability are made public on our issue tracker 90 days after the release in which they were patched. We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post.

Recommended Action

We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible. When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, it means all types are affected.

Security fixes

Table of security fixes

TitleSeverity Code Injection issue via GraphQL directive impacts GitLab CE/EECritical Cross-Site Request Forgery issue in GraphQL multiplex query handler impacts GitLab CE/EEHigh

CVE-2026-19478 - Code Injection issue via GraphQL directive impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could allow an unauthenticated user to remotely modify or delete public projects and user data via a GraphQL directive. Impacted Versions: GitLab CE/EE: all versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4CVSS 9.4 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H) Thanks hiimguardian for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-19650 - Cross-Site Request Forgery issue in GraphQL multiplex query handler impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an unauthenticated user to execute mutations via GET requests due to improper request validation in GraphQL multiplex query handling. Impacted Versions: GitLab CE/EE: all versions from 18.2 before 18.11.11, 19.0 before 19.0.8, 19.1 before 19.1.6, and 19.2 before 19.2.4CVSS 7.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:L) Thanks kreep for reporting this vulnerability through our HackerOne bug bounty program.

Important notes on upgrading

These versions do not include any new migrations, and for multi-node deployments, should not require any downtime. Please be aware that by default the Omnibus packages will stop, run migrations, and start again, no matter how “big” or “small” the upgrade is. This behavior can be changed by adding a /etc/gitlab/skip-auto-reconfigure file, which is only used for updates.

Updating

To update GitLab, see the Update page. To update GitLab Runner, see the Updating the Runner page.

Receive Patch Notifications

To receive patch blog notifications delivered to your inbox, visit our contact us page. To receive release notifications via RSS, subscribe to our patch release RSS feed or our RSS feed for all releases.

Help us learn about your current experience with the documentation. Take the survey.

On August 12, 2026, we released versions 19.2.2, 19.1.4, 19.0.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, please visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here. For security fixes, the issues detailing each vulnerability are made public on our issue tracker 90 days after the release in which they were patched. We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post.

Recommended Action

We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible. When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, it means all types are affected.

Security fixes

Table of security fixes

TitleSeverity Cross-site Scripting issue in Analytics Dashboards table field configuration impacts GitLab CE/EEHigh Cross-site Scripting issue in Analytics Dashboards pagination controls impacts GitLab CE/EEHigh Remote code execution via path traversal in package registry impacts GitLab CE/EEHigh Improper Authorization issue in CI/CD pipeline API impacts GitLab CE/EEHigh Authorization Bypass issue in Duo Workflow Service impacts GitLab EEHigh Cross-site Scripting issue in CI manual job confirmation modal impacts GitLab CE/EEHigh Missing Authorization issue in ProjectsController impacts GitLab EEHigh Denial of Service issue in GraphQL API JSON parser impacts GitLab CE/EEMedium Missing Authorization issue in merge requests API impacts GitLab EEMedium Missing Authorization issue in external status check API impacts GitLab EEMedium Incorrect Authorization issue in npm dist-tags endpoint impacts GitLab CE/EEMedium Missing Authorization issue in GitLab Duo settings page impacts GitLab EEMedium Incorrect Authorization issue in AI Tool Rules GraphQL resolver impacts GitLab EEMedium Incorrect Privilege Assignment issue in custom roles impacts GitLab EELow

CVE-2026-15217 - Cross-site Scripting issue in Analytics Dashboards table field configuration impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed cross-site scripting due to improper neutralization of user-controlled values rendered in table cell content by an analytics dashboard component. Impacted Versions: GitLab CE/EE: all versions from 18.2 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2CVSS 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-15216 - Cross-site Scripting issue in Analytics Dashboards pagination controls impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed cross-site scripting due to improper neutralization of user-controlled data rendered in pagination controls by an analytics dashboard component. Impacted Versions: GitLab CE/EE: all versions from 18.2 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2CVSS 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-10053 - Remote code execution via path traversal in package registry impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to achieve remote code execution due to a path traversal vulnerability in the package registry. Impacted Versions: GitLab CE/EE: all versions from 18.8 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2CVSS 8.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H) Thanks invisiblemeerkat for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-15423 - Improper Authorization issue in CI/CD pipeline API impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with developer-role permissions to execute CI/CD pipelines on a protected branch without the required push permissions due to improper authorization in pipeline reference validation. Impacted Versions: GitLab CE/EE: all versions from 19.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2CVSS 8.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N) Thanks sim4n6 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-19228 - Authorization Bypass issue in Duo Workflow Service impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to cause AI usage to be attributed to another namespace, due to improper authorization of identity information supplied in requests. Impacted Versions: GitLab EE: all versions from 19.1 before 19.1.4 and 19.2 before 19.2.2CVSS 8.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L) This vulnerability was discovered internally by GitLab team member Dennis Appelt

CVE-2026-16627 - Cross-site Scripting issue in CI manual job confirmation modal impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with developer-role permissions to escalate privileges due to improper sanitization of HTML content rendered in a CI job modal. Impacted Versions: GitLab CE/EE: all versions from 19.2 before 19.2.2CVSS 7.7 (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N) Thanks 3nvz for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-16494 - Missing Authorization issue in ProjectsController impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to modify project settings restricted to higher-privileged roles, due to missing authorization checks on a project update endpoint. Impacted Versions: GitLab EE: all versions from 19.1 before 19.1.4 and 19.2 before 19.2.2CVSS 7.1 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L) Thanks 3nvz for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-7427 - Denial of Service issue in GraphQL API JSON parser impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an unauthenticated user to cause a denial of service due to improper input validation. Impacted Versions: GitLab CE/EE: all versions from 18.5 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L) Thanks aphantom for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-6821 - Missing Authorization issue in merge requests API impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to bypass IP-based access restrictions and read limited merge request information from a private project due to missing authorization checks in a merge requests API endpoint. Impacted Versions: GitLab EE: all versions from 12.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks rogerace for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-4879 - Missing Authorization issue in external status check API impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with developer-role permissions to view external status check configuration restricted to higher-privileged roles due to missing authorization on a merge request API endpoint. Impacted Versions: GitLab EE: all versions from 16.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks jaykp for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-8667 - Incorrect Authorization issue in npm dist-tags endpoint impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with developer role to modify certain package registry metadata without the required maintainer-level permissions due to improper authorization checks. Impacted Versions: GitLab CE/EE: all versions from 17.6 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) Thanks peppersghost for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-18244 - Missing Authorization issue in GitLab Duo settings page impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to view restricted configuration settings due to improper authorization checks on a group settings page. Impacted Versions: GitLab EE: all versions from 17.7 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) This vulnerability has been discovered internally by GitLab team member Félix Veillette-Potvin

CVE-2026-18433 - Incorrect Authorization issue in AI Tool Rules GraphQL resolver impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to read policy configuration belonging to a namespace they were not authorized to access, due to incorrect authorization checks in a GraphQL query. Impacted Versions: GitLab EE: all versions from 19.1 before 19.1.4 and 19.2 before 19.2.2CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks anshuman_bh for reporting this vulnerability through our HackerOne bug bounty program

CVE-2025-9486 - Incorrect Privilege Assignment issue in custom roles impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed a user with a pending membership to receive permissions granted by a custom role, due to incorrect privilege assignment that did not account for membership state. Impacted Versions: GitLab EE: all versions from 15.6 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2CVSS 3.3 (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N) Thanks mateuszek for reporting this vulnerability through our HackerOne bug bounty program

Bug fixes

19.2.2

• Backport of “Gate resolve-dependency-bump button to dependency bot MRs” to 19.2
• Backport of ‘Skip EventWorker enqueue in the Geo Log Cursor when sync_object_storage is disabled on the current node’
• Stop validating web_hook_logs_daily sharding key constraint (19.2 backport)
• Backport: Push agent_artifacts_page flag on project settings edit page
• Backport of ‘Sign Workhorse MCP client requests with the API JWT’
• Backport of ‘Pre-approve Orbit MCP tools in tool_access_policies claim’
• Remove headers within content tabs
• Backport of ‘Pre-approve GitLab MCP server read tools in the token claim’
• Backport Setup Siphon users rake task
• 19.2 Backport of ‘Fix 500 when securityReportFindings cursor is empty string’
• Fix work item drawer Open in full page on issue boards (backport to 19.2) …

Help us learn about your current experience with the documentation. Take the survey.

On August 6, 2026, we released versions 18.11.9 for GitLab Community Edition and Enterprise Edition. These versions resolve a number of regressions and bugs. This patch release does not include any security fixes.

GitLab Community Edition and Enterprise Edition

18.11.9

We have pulled the omnibus install of 18.11.8 and replaced it with 18.11.9. A bug was found in the deprecation code that enabled Mattermost incorrectly. If you have a local cache of our omnibus package, you will want to remove 18.11.8 and get 18.11.9.

• Update gitlab-logger to v4.0.1 (18-11-stable)
• Backport of ‘Keep virtual registry settings toggle visible when disabled’ into 18.11
• Backport of “Fix blob preview diff hiding blank added lines”
• Backport of ‘Backfill duo_secret_detection_fp_enabled to false’
• [18.11] Backport of “Remove –unlink-first and –recursive-unlink from tar extract”
• Backport of ‘Add postgres_index_bloat_estimate SQL function’
• [18.11 Backport] Bump PostgreSQL versions to 16.14 and 17.10
• Backport fix for Mattermost deprecation to 18.11
• Fix accidental enable of mattermost by deprecation check -> in 18.11.9

Important notes on upgrading

This patch includes database migrations that may impact your upgrade process. Postgresql server versions were updated to 16.14 and 17.10 to include the latest upstream patches and fixes. This version fixes an issue where upgrading to 19.x failed with a Mattermost deprecation error for Linux package installations, even when Mattermost was not actively configured. Upgrade to this version before upgrading to 19.0 or later. For details, see Mattermost removed from the Linux package. On very large installations, the gitlab:db:reindex task could time out while estimating index bloat for a single index, causing the job to fail repeatedly and leaving PostgreSQL indexes to grow increasingly bloated, which in turn degraded overall instance performance and complicated upgrades. This release restructures the bloat-estimation query for single-index lookups, restoring reliable automatic reindexing on large databases.

Impact on your installation:

• Single-node instances: This patch will cause downtime during the upgrade as migrations must complete before GitLab can start.
• Multi-node instances: With proper zero-downtime upgrade procedures, this patch can be applied without downtime.

Regular migrations

The following version includes regular migrations that run during the upgrade process:

• 18.11.9

Post-deploy migrations

The following version includes post-deploy migrations that can run after the upgrade:

• 18.11.9 To learn more about the impact of upgrades on your installation, see:
• Zero-downtime upgrades for multi-node deployments
• Standard upgrades for single-node installations

Updating

To update, check out our update page.

GitLab subscriptions

Access to GitLab Premium and Ultimate features is granted by a paid subscription. Alternatively, sign up for GitLab.com to use GitLab’s own infrastructure.

Help us learn about your current experience with the documentation. Take the survey.

On July 29, 2026, we released versions 19.2.1, 19.1.3, 19.0.5 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, please visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here. For security fixes, the issues detailing each vulnerability are made public on our issue tracker 90 days after the release in which they were patched. We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post.

Recommended Action

We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible. When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, it means all types are affected.

Security fixes

Table of security fixes

TitleSeverity Sensitive Information Exposure issue in Workhorse impacts GitLab CE/EEHigh Mass Assignment issue in Pipeline Schedule API impacts GitLab CE/EEHigh Denial of Service issue in Merge Request Discussions impacts GitLab CE/EEHigh Race Condition issue in merge request approval rules impacts GitLab EEMedium Insufficiently Protected Credentials issue in Virtual Registries impacts GitLab EEMedium Improper Access Control issue in project import status impacts GitLab CE/EEMedium Improper Authorization issue in project import functionality impacts GitLab CE/EEMedium Cross-site Scripting issue in paginated views impacts GitLab CE/EEMedium Prompt Injection issue in Duo Code Review impacts GitLab EEMedium Incorrect Security Token Generation issue in Duo Workflows impacts GitLab EEMedium Exposure of Sensitive Information issue in merge request title generation impacts GitLab CE/EEMedium Improper Access Control issue in Pipeline Test Report API impacts GitLab CE/EEMedium Incorrect Authorization issue in merge request collaboration settings impacts GitLab CE/EELow

CVE-2026-6267 - Sensitive Information Exposure issue in Workhorse impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with Developer role to access unauthorized information due to insufficient access controls on internal request handling. Impacted Versions: GitLab CE/EE: all versions from 10.1.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1CVSS 8.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H) Thanks thwin_htet for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-12436 - Mass Assignment issue in Pipeline Schedule API impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to modify CI/CD configuration belonging to another user due to improper validation of user-supplied attributes when processing pipeline schedule inputs. Impacted Versions: GitLab CE/EE: all versions from 18.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1CVSS 8.4 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:L) Thanks a0xnirudh for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-15975 - Denial of Service issue in Merge Request Discussions impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an unauthenticated user to cause a denial of service due to insufficient resource throttling when processing merge request discussions. Impacted Versions: GitLab CE/EE: all versions from 11.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) This vulnerability has been discovered internally by GitLab team member Hordur Freyr Yngvason

CVE-2026-13113 - Race Condition issue in merge request approval rules impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to merge code into a protected branch without the required approvals due to a race condition in approval rule processing. Impacted Versions: GitLab EE: all versions from 17.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) This vulnerability has been discovered internally by GitLab team member Niklas Janz

CVE-2026-16553 - Insufficiently Protected Credentials issue in Virtual Registries impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed some sensitive information to be disclosed to an unintended host due to improper handling of upstream requests in virtual registries. Impacted Versions: GitLab EE: all versions from 18.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1CVSS 5.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L) This vulnerability has been discovered internally by GitLab team member Fiona McCawley

CVE-2026-6336 - Improper Access Control issue in project import status impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an unauthorized user to view project import source information due to a missing authorization check. Impacted Versions: GitLab CE/EE: all versions from 16.6 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) Thanks 3nvz for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-14341 - Improper Authorization issue in project import functionality impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with Maintainer role to modify protected branch configuration due to improper authorization in a projects API endpoint. Impacted Versions: GitLab CE/EE: all versions from 12.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1CVSS 4.9 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N) Thanks slide123 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-3093 - Cross-site Scripting issue in paginated views impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an attacker to execute arbitrary JavaScript in another user’s browser via a crafted URL, due to improper sanitization of user-controlled input. Impacted Versions: GitLab CE/EE: all versions from 14.0 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1CVSS 4.7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N) Thanks go7f0 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-15077 - Prompt Injection issue in Duo Code Review impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to access information from unauthorized projects due to improper neutralization of untrusted content processed by the AI-assisted code review functionality. Impacted Versions: GitLab EE: all versions from 19.1 before 19.1.3 and 19.2 before 19.2.1CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) This vulnerability has been discovered internally by GitLab team member Mike Wronski

CVE-2026-15831 - Incorrect Security Token Generation issue in Duo Workflows impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to bypass administrator-configured tool governance policies due to improper authorization enforcement during token generation. Impacted Versions: GitLab EE: all versions from 19.1 before 19.1.3 and 19.2 before 19.2.1CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) This vulnerability has been discovered internally by GitLab team member Dennis Appelt

CVE-2026-14351 - Exposure of Sensitive Information issue in merge request title generation impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an unauthenticated user to view the title of a confidential issue through a publicly accessible merge request due to improper authorization checks. Impacted Versions: GitLab CE/EE: all versions from 8.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks toofikz for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-4672 - Improper Access Control issue in Pipeline Test Report API impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with guest-role permissions to access test report contents they were not authorized to view due to improper access control enforcement. Impacted Versions: GitLab CE/EE: all versions from 18.4 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks rogerace for reporting this vulnerability through our HackerOne bug bounty program

CVE-2025-14562 - Incorrect Authorization issue in merge request collaboration settings impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with developer-role permissions to commit changes to a project after being removed as a member, due to improper authorization checks on merge request collaboration settings. Impacted Versions: GitLab CE/EE: all versions from 10.6 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1CVSS 3.1 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N) Thanks theluci for reporting this vulnerability through our HackerOne bug bounty program

Bug fixes

19.2.1

• Backport final 19.2 release notes
• [19.2] Backport of “Remove –unlink-first and –recursive-unlink from tar extract”
• [19.2] Backport of Revert “Merge branch ‘jmd/fix-merge-request-reapprove-reunapprove’ into ‘master’”
• Backport “Enforce admin Duo lock on group settings update” to 19.2
• Backport of ‘Fix keys.organization_id NOT NULL constraint failure on Self-Managed/Dedicated upgrades’ to 19.2
• 19.2 backport of feat(danger): Block post-deploy migrations on security MRs
• [19.2] Delete orphaned caches in helm metadata cache backfill
• Backport ‘Restore AI infrastructure settings after 19.2 upgrades’ to 19-2-stable-ee
• Backport of ‘Fix HTTP_V2 config leak breaking unrelated specs’
• Backport of “Fix self-hosted DWS TLS setting ignored in flow validation and metadata”
• Backport of ‘Fix self-managed admin/owner cannot enroll namespaces into Orbit’
• Backport of ‘Enable Orbit and Knowledge Graph feature flags by default’
• Backport of Fix silent data loss in Advanced Search routing for >128 root_ancestor_ids

19.1.3

• Update gitlab-logger to v4.0.1 (19-1-stable)
• Backport of “Allow AIGW timeout setting on GitLab Dedicated instances”
• Backport of “Fixes the Copy commit SHA button in commits list”
• Backport of ‘Keep virtual registry settings toggle visible when disabled’ into 19.1
• Merge branch ‘ss/revert-cb7f0fd33375’ into ‘master’
• Backport of “Fix blob preview diff hiding blank added lines”
• Fix nil error when checking checkpoints that are not fully instantiated (19-1 backport) …

Help us learn about your current experience with the documentation. Take the survey.

On July 16, 2026, GitLab 19.2 was released with the following features. We are excited to recognize vivekshukl007 as this month’s Notable Contributor! Vivek is a Senior Data Engineer at Emirates who made a high-impact contribution to add Scala language support to GitLab Orbit. This change improves the code graph capabilities for developers who work in Scala codebases.

Primary features

GitLab Duo CLI is now generally available

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue GitLab Duo CLI brings the GitLab Duo Agent Platform directly to your terminal. Use the CLI to ask complex questions about your codebase and to autonomously perform actions on your behalf. Unlike external tools, the CLI has context about your GitLab project, pipelines, and agent configurations. Key features include:
• Two modes: interactive chat mode and headless mode for CI/CD
• Administrator on/off control for GitLab Self-Managed and GitLab Dedicated
• Model selection and shared sessions
• Tool approvals
• Model Context Protocol (MCP) connections
• Slash commands, including commands for context usage and context compaction
• Support for skills and AGENTS.md customization files Install the GitLab Duo CLI through the GitLab CLI (glab) or as a standalone tool.

GitLab Duo custom flows are now generally available

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue Custom flows are AI-powered workflows you create and configure to automate complex, multi-step tasks across your GitLab projects. They let teams define workflow steps, components, and triggers so repetitive development and operational work can run automatically in response to GitLab events. In the GitLab UI, flows run directly in GitLab CI/CD, helping teams automate common tasks without leaving GitLab. Key features include:
• YAML-defined, reusable workflows for team-specific automation
• Multi-agent orchestration for complex, multi-step tasks
• User-defined human-in-the-loop (HITL) checkpoints for approval or feedback at sensitive steps
• Native GitLab triggers, including mentions, assignments, pipeline events, and merge request lifecycle events
• Flow creation and management from projects or the AI Catalog
• Public and private visibility controls
• Secure execution using service accounts and composite identity
• YAML validation to catch configuration issues before runtime

Scheduled pipeline execution policies are GA

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue Scheduled pipeline execution policies are now generally available. Define a schedule once in a security policy project and enforce it across every project in scope, without editing each project’s .gitlab-ci.yml. If requirements change, update the policy in one place instead of coordinating changes across many CI/CD configuration files. Use scheduled policies to run compliance scripts, security scans, or other custom CI/CD jobs on a daily, weekly, or monthly cadence, independent of commit activity. This is useful for repositories without regular code changes, such as running dependency scans to detect newly discovered vulnerabilities. Each policy runs as a separate pipeline, with time zone support, time window distribution, and branch targeting.

Start foundational flows from Agentic Chat

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue In previous versions of GitLab, you started foundational flows from specific UI actions, mentions, or assignments. Now you can start them from Agentic Chat in the GitLab UI as part of your conversation. When your request matches a specialist workflow, Agentic Chat hands off to one of these flows:
• Developer Flow: Implements changes or opens a merge request
• Code Review Flow: Reviews a merge request
• Fix CI/CD Pipeline Flow: Diagnoses and repairs a failed pipeline You approve the handoff in chat, then follow progress in the conversation or from AI > Sessions.

Dependency scanning auto-remediation (Beta)

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue GitLab 19.2 introduces Dependency scanning auto-remediation in Beta. The feature brings automated vulnerability remediation directly into your dependency scanning workflow, with two capabilities:
• Automated dependency version bumps, available on GitLab.com, GitLab Self-Managed, and GitLab Dedicated.
• Agentic Breaking Change Resolution, available on GitLab.com, GitLab Self-Managed, and GitLab Dedicated, and consumes GitLab Credits. Automated dependency version bumps automatically opens merge requests to update vulnerable dependencies to their safe versions. Once turned on, GitLab monitors your projects for vulnerable dependencies and opens remediation MRs without manual intervention. By default, updates target patch and minor versions. Agentic Breaking Change Resolution extends the remediation flow to handle complex updates. When a merge request that bumps dependency versions has a pipeline fails on a breaking change, GitLab Duo analyzes the pipeline errors, the dependency’s changelog, and how your code uses the dependency. GitLab Duo commits fixes to the same MR and re-runs the pipeline until the pipeline passes. When you enable Agentic Breaking Change Resolution, version bumps extend to include major versions. Together, the two capabilities form a complete remediation loop: GitLab opens the MR, and when the update is complex, GitLab Duo resolves it. For setup instructions, see Dependency scanning auto-remediation. Share feedback in the beta feedback issue.

Non default branch tracking (beta)

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue You can now track vulnerabilities on branches other than the default branch. For the best results, target a small number of long-lived release branches, such as branches for specific environments (project-qa, project-prod) or deployment platforms (project-iOS, project-android). This beta includes the following capabilities:
• Add tracked branches on the security configuration page, up to twice the number of projects in the namespace.
• Filter by branch on the vulnerability report.
• Filter by branch on the project-level security dashboard.
• Track all vulnerability types on tracked branches, including CVEs, which were previously out of scope.
• Keep vulnerability status metadata consistent when a branch merges into the default branch.
• Update vulnerability status on tracked branches.

Selective GitLab Duo availability for subgroups

• Tier: Ultimate
• Offering: GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation · Related Issue Administrators of GitLab Dedicated instances can make GitLab Duo and GitLab Duo Agent Platform unavailable for selected subgroups while other subgroups still have the option to turn them on. Previously, you could either disable GitLab Duo and Agent Platform for an entire instance, or make them potentially available for all. Now you can enforce a default-deny, per-subgroup allowlist. Mark specific subgroups as Always off (locked) so their descendant groups and projects can never enable GitLab Duo and Agent Platform, while leaving other subgroups up to the discretion of users with the Owner role. Only administrators can apply or remove the lock, and affected Owners see clear messaging that GitLab Duo is locked by a parent group. This feature helps compliance and platform governance teams meet strict data-classification requirements.

AI audit event report (beta)

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation · Related Issue AI audit event reports are now available in beta, giving security and compliance teams a unified, downloadable record of GitLab Duo agent activity. Previously, agent activity was scattered across pipeline jobs and event histories, making it difficult to reconstruct a session for:
• Incident investigation.
• Compliance review.
• AI governance reporting. Now, each agent session produces a comprehensive audit artifact capturing:
• Inputs.
• Model and configuration context.
• The chronological event timeline.
• Outputs. You can browse AI audit events from the Governance page, filter by agent and session details, drill into individual events, and download the underlying session artifact.

Security Review Flow (beta)

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue Security Review Flow detects business logic vulnerabilities directly in merge requests. Unlike static analysis tools that scan for known patterns, Security Review Flow reasons about the intent of your code and identifies authorization bypasses, data exposure, and logic errors that pattern-based scanners routinely miss. To request a review, assign the Duo Security Review service account as a reviewer on your merge request. The flow analyzes the diff and posts findings as threaded comments at the exact lines where vulnerabilities occur, each with a Common Weakness Enumeration (CWE) classification, severity rating, and where possible, an inline suggested fix you can apply without leaving the merge request. Each review consumes GitLab Credits based on the complexity of the merge request diff.

Agentic Core

Bulk AI Catalog items enablement

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation · Related Issue When enabling public custom and external agents and public custom flows in the AI Catalog, you can now select up to 100 projects in a single action, instead of selecting individual projects one at a time.

Configure ID tokens in flows

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation · Related Issue Use ID tokens to authenticate with third-party OpenID Connect (OIDC) services without storing long-lived credentials. For example, use ID tokens for keyless signing of binaries and commits, or to retrieve secrets from a secrets manager. To use this feature, update your agent configuration to include the id_tokens keyword, then configure the service to trust tokens issued by GitLab Duo Agent Platform.

Custom Agent validation

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue Previously, you could save a custom agent in AI Catalog whose prompt would fail when run. For example, prompts that tripped security rules caused the agent to silently do nothing when being used. Now, when you create or update a custom agent, GitLab validates the prompt configuration, and tells you about any errors before you save that agent.

Turn on MCP server independently from the Agent Platform

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation · Related Issue To give you finer control over how external tools connect to your GitLab instance or group, you can now turn the GitLab MCP server on or off independently from Agent Platform settings. …

Help us learn about your current experience with the documentation. Take the survey.

On July 8, 2026, we released versions 19.1.2, 19.0.4, 18.11.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, please visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here. For security fixes, the issues detailing each vulnerability are made public on our issue tracker 90 days after the release in which they were patched. We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post.

Recommended Action

We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible. When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, it means all types are affected.

Security fixes

Table of security fixes

TitleSeverity Cross-site Scripting issue in vulnerability evidence table renderer impacts GitLab EEHigh HTML Injection in wiki markup rendering impacts GitLab CE/EEHigh Insufficiently Protected Credentials issue in repository mirroring impacts GitLab EEMedium Improper Access Control issue in work items impacts GitLab EEMedium Missing Authorization issue in commit discussion display impacts GitLab CE/EEMedium Ambiguity Reference issue in a tag or branch impacts GitLab CE/EELow Incorrect Authorization issue in group-level settings impacts GitLab EELow Incorrect Authorization issue in compliance violation management impacts GitLab EELow

CVE-2026-6896 - Cross-site Scripting issue in vulnerability evidence table renderer impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with developer-role permissions to execute arbitrary scripts in another user’s browser session due to improper sanitization of user-supplied input. Impacted Versions: GitLab EE: all versions from 13.11 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2CVSS 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-13320 - HTML Injection in wiki markup rendering impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to execute arbitrary scripts in another user’s browser session due to improper sanitization of user-supplied input. Impacted Versions: GitLab CE/EE: all versions from 15.7 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2CVSS 7.3 (CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N) Thanks youzslan and a_m_a_m for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-11827 - Insufficiently Protected Credentials issue in repository mirroring impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with maintainer-role permissions to obtain another user’s stored credentials due to improper authorization controls. Impacted Versions: GitLab EE: all versions from 9.5 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2CVSS 4.9 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N) Thanks rogerace for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-8472 - Improper Access Control issue in work items impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with minimal access permissions to read work item metadata from private projects due to missing authorization checks. Impacted Versions: GitLab EE: all versions from 18.9 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks go7f0 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-7492 - Missing Authorization issue in commit discussion display impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an unauthenticated user to determine the existence of a private project due to improper authorization controls on cross-project reference pages. Impacted Versions: GitLab CE/EE: all versions from 9.1 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks nathanaelhoun for reporting this vulnerability through our HackerOne bug bounty program

CVE-2025-12506 - Ambiguity Reference issue in a tag or branch impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to create a repository where the content displayed in the web interface differed from the content available for download, due to improper handling of Git reference name resolution. Impacted Versions: GitLab CE/EE: all versions from 16.5 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2CVSS 3.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N) Thanks shells3c for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-13151 - Incorrect Authorization issue in group-level settings impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to modify group-level settings beyond their intended permissions due to improper authorization controls. Impacted Versions: GitLab EE: all versions from 16.10 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2CVSS 2.7 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N) This vulnerability has been discovered internally by GitLab team member zli

CVE-2026-6352 - Incorrect Authorization issue in compliance violation management impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with auditor-level access to modify compliance violation records due to improper authorization on certain GraphQL operations. Impacted Versions: GitLab EE: all versions from 18.2 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2CVSS 2.7 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N) Thanks amanverasia for reporting this vulnerability through our HackerOne bug bounty program

Bug fixes

19.1.2

• Set organization_id when registering OAuth applications (19.1 backport)
• Bump Go to 1.25.11
• Backport of ‘Fix 500 on multi-arch tags on the legacy registry path’ into 19.1
• Backport of “Use commit author and committer identity for external agent flows”
• Backport of ‘Make ci_finished_builds engine swap work on ClickHouse 23.x’ into 19.1
• Backport of ‘Limit getDuoWorkflowEvents to latest checkpoint with cursor pagination’ into 19.1
• Backport of ‘Backfill NULL organization_id on oauth_applications before constraint validation’ to 19.1
• Backport: Revert the MR 238702
• Backport of “Remove ActiveUserCountThresholdWorker cron schedule” into 19.1
• Backport of ‘Fix approval rule override regression for Developer MR authors’
• Backport of Fix commits page memory leak from eager description fetch
• Pass organization_id when creating OAuth Applications
• Add BUILDER_IMAGE_REVISION to 5.60.1

19.0.4

• Set organization_id when registering OAuth applications (19.0 backport)
• Backport: Skopeo auth to registry, via CI_JOB_TOKEN (19-0-stable)
• Bump Go to 1.25.11
• Backport of “Add composite identity checks for commit”
• Backport of “Use commit author and committer identity for external agent flows”
• Backport of ‘Fix ci_finished_builds engine swap on deferred post-deploy’ into 19.0
• Backport of ‘Limit getDuoWorkflowEvents to latest checkpoint with cursor pagination’ into 19.0
• Backport of ‘Backfill NULL organization_id on oauth_applications before constraint validation’ to 19.0
• Quarantine flaky user_suggests_changes_on_diff_spec examples
• Backport shared example fix in 19-0-stable-ee
• Deflake granular token permissions spec for group MRs
• Pass organization_id when creating OAuth Applications
• Add BUILDER_IMAGE_REVISION to 5.57.1

18.11.7

• Fix fetch_assets to authenticate skopeo inspect for private registries
• Bump Go to 1.25.11
• Backport of ‘Fix ci_finished_builds engine swap on deferred post-deploy’ into 18.11
• Backport of ‘Limit getDuoWorkflowEvents to latest checkpoint with cursor pagination’ into 18.11
• Quarantine flaky user_suggests_changes_on_diff_spec examples
• [18.11] Mattermost Security Updates June 12, 2026
• backport: add mattermost and spamcheck deprecation entries to 18.11
• Add BUILDER_IMAGE_REVISION to 5.52.1

Important notes on upgrading

This patch includes database migrations that may impact your upgrade process.

Impact on your installation:

• Single-node instances: This patch will cause downtime during the upgrade as migrations must complete before GitLab can start.
• Multi-node instances: With proper zero-downtime upgrade procedures, this patch can be applied without downtime.

Post-deploy migrations

The following versions include post-deploy migrations that can run after the upgrade:

• 19.1.2
• 19.0.4 To learn more about the impact of upgrades on your installation, see:
• Zero-downtime upgrades for multi-node deployments
• Standard upgrades for single-node installations

Updating

To update GitLab, see the Update page. To update GitLab Runner, see the Updating the Runner page.

Receive Patch Notifications

To receive patch blog notifications delivered to your inbox, visit our contact us page. To receive release notifications via RSS, subscribe to our patch release RSS feed or our RSS feed for all releases.

Help us learn about your current experience with the documentation. Take the survey.

On July 1, 2026, we released version 18.8.11 for GitLab Community Edition and Enterprise Edition. These versions resolve regressions and bugs. This patch release does not include any security fixes. When database load balancing is in use, database connections may not be returned to the pool as a result of a regression caused by the upgrade to Rails 7.2. We are making an out-of-band patch release to ensure stability for customers upgrading to the required stop of GitLab 18.8.

GitLab Community Edition and Enterprise Edition

18.8.11

• Fix database connection leaks when database load balancer in use

Important notes on upgrading

This version does not include any new migrations, and for multi-node deployments, should not require any downtime. Please be aware that by default the Omnibus packages will stop, run migrations, and start again, no matter how “big” or “small” the upgrade is. This behavior can be changed by adding a /etc/gitlab/skip-auto-reconfigure file, which is only used for upgrades.

Updating

To update, check out our update page.

GitLab subscriptions

Access to GitLab Premium and Ultimate features is granted by a paid subscription. Alternatively, sign up for GitLab.com to use the GitLab infrastructure.

Help us learn about your current experience with the documentation. Take the survey.

On June 24, 2026, we released versions 19.1.1, 19.0.3, 18.11.6 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, please visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here. For security fixes, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched. We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post.

Recommended Action

We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible. When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, it means all types are affected.

Security fixes

Table of security fixes

TitleSeverity Cross-site Scripting issue in Analytics Dashboard impacts GitLab EEHigh Cross-site Scripting issue in Web IDE workbench asset handler impacts GitLab CE/EEHigh Information Disclosure issue in Duo Workflows impacts GitLab EEHigh Authorization Bypass issue in Virtual Registry Cleanup Policy API impacts GitLab EEMedium Improper Authorization issue in Rapid Diffs impacts GitLab CE/EEMedium Incorrect Authorization issue in DAST scanner and site profile management impacts GitLab EEMedium Insufficient Filtering issue in CI/CD API impacts GitLab CE/EEMedium Improper Input Validation issue in Snippets impacts GitLab CE/EEMedium Incorrect Authorization issue in Maven Package Registry impacts GitLab CE/EEMedium Improper Access Control issue in group packages API impacts GitLab CE/EEMedium Improper Access Control issue in Protected Environments API impacts GitLab EELow Missing Authorization issue in Security Dashboard impacts GitLab EELow Server-Side Request Forgery issue in Repository Mirroring impacts GitLab CE/EELow

CVE-2026-10086 - Cross-site Scripting issue in Analytics Dashboard impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with developer-role permissions to execute arbitrary client-side code in the context of another user’s session, due to improper sanitization of user-supplied input. Impacted Versions: GitLab EE: all versions from 16.4 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1CVSS 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-10712 - Cross-site Scripting issue in Web IDE workbench asset handler impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an unauthenticated user to execute arbitrary JavaScript in a user’s browser session due to improper path validation under certain conditions. Impacted Versions: GitLab CE/EE: all versions from 18.10 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1CVSS 8.0 (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N) Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-12053 - Information Disclosure issue in Duo Workflows impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed a user to access sensitive information that had already been committed to a project, due to insufficient output filtering in Duo Workflows. Impacted Versions: GitLab EE: all versions from 19.1 before 19.1.1CVSS 7.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N) Thanks 3nvz and GitLab team member Dennis Appelt for reporting this vulnerability

CVE-2026-5309 - Authorization Bypass issue in Virtual Registry Cleanup Policy API impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to read or modify another group’s virtual registry cleanup policy settings without authorization. Impacted Versions: GitLab EE: all versions from 18.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1CVSS 5.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) Thanks go7f0 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-2238 - Improper Authorization issue in Rapid Diffs impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an unauthenticated user to view confidential issue references on public projects due to improper authorization checks. Impacted Versions: GitLab CE/EE: all versions from 17.5 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) Thanks modhanami for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-11379 - Incorrect Authorization issue in DAST scanner and site profile management impacts GitLab EE

GitLab has remediated an issue in GitLab EE affecting all versions from 13.11 prior to 18.11.6, 19.0 prior to 19.0.3, and 19.1 prior to 19.1.1 in which incorrect authorization in DAST site profile management could allow a user with Developer role to exfiltrate DAST site profile secrets under certain conditions. Impacted Versions: GitLab EE: all versions from 13.11 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1CVSS 5.3 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N) This vulnerability has been discovered internally by GitLab team member David Nelson

CVE-2026-8330 - Insufficient Filtering issue in CI/CD API impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed sensitive information to be written to application logs due to insufficient filtering in a CI/CD API endpoint. Impacted Versions: GitLab CE/EE: all versions from 9.3 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1CVSS 4.4 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N) This vulnerability has been discovered internally by GitLab team member Joel Clarke

CVE-2026-1606 - Improper Input Validation issue in Snippets impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to conceal content within a Snippet due to improper input validation. Impacted Versions: GitLab CE/EE: all versions from 14.8 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) Thanks st4nly0n for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-5952 - Incorrect Authorization issue in Maven Package Registry impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with developer-role permissions to bypass package protection rules and overwrite protected Maven package metadata due to incorrect authorization checks. Impacted Versions: GitLab CE/EE: all versions from 17.11 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) Thanks pkkr for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-5796 - Improper Access Control issue in group packages API impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with Reporter-level group permissions to view package metadata from projects with the Package Registry disabled due to incorrect authorization checks in the group packages feature. Impacted Versions: GitLab CE/EE: all versions from 13.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks harshinsecurity for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-0934 - Improper Access Control issue in Protected Environments API impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with custom role permissions to view, create, or delete protected environment configurations despite CI/CD visibility being disabled for the project. Impacted Versions: GitLab EE: all versions from 17.9 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1CVSS 3.8 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N) Thanks vulnable for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-3176 - Missing Authorization issue in Security Dashboard impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with limited permissions to access project information due to insufficient authorization checks. Impacted Versions: GitLab EE: all versions from 18.6 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1CVSS 3.1 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks modestia for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-12635 - Server-Side Request Forgery issue in Repository Mirroring impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with maintainer-role permissions to make requests to internal network resources through mirror synchronization due to improper URL validation. Impacted Versions: GitLab CE/EE: all versions from 8.3 before 18.11.6, 19.0 before 19.0.3, and 19.1 before 19.1.1CVSS 3.1 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N) This vulnerability has been discovered internally by GitLab team member Félix Veillette-Potvin

Bug fixes

19.1.1

• Backport final 19.1 release notes
• Backport fix flaky N+1 REST API spec
• [19.1] Backport of Revert “Merge branch ‘587231-update-session-list-item-format’ into ‘master’”
• Backport of “Remove GIT_CONFIG_GLOBAL=/dev/null from Duo Workflow git hardening”
• Backport of ‘Fix wrong argument’
• Exclude .agents and .claude dirs from gitlab-rails package
• [19.1] Normalize falsey smtp_authentication to disable SMTP auth
• Backport SLES 15.6 extended support into 19-1-stable

19.0.3

• Update yq to 4.53.3 - Backport to 19-0
• 19-0 Backport: Update azcopy to version 10.32.4
• 19-0 Backport: Update PyOpenSSL to 25.3.0 and pin python-cryptography to 46.0.7
• Backport of ‘Filter group template projects by user visibility and membership’
• Backport of “Treat split failure reasons as retry:when aliases”
• Backport of ‘Allow URL import into groups when personal project creation disabled’ to 19.0
• 19.0 Backport of ‘Add index on security_findings for keyset pagination’
• Backport of ‘Fix Amazon Q usage quota check’ into 19.0
• Backport of ‘Fix 500 on multi-arch tags on the legacy registry path’ into 19.0
• Backport ‘Restore admin-level user data read access for auditors in Users API’ to 19.0
• Backport: Fix UUID calibration with multiple branch tracking
• Backport of ‘Fix: Embeddings Indexing: nil user error in embeddings client’
• [19.0] Backport of Revert “Merge branch ‘587231-update-session-list-item-format’ into ‘master’”
• Backport of “fix: Fix malformed safe.directory in workflows”
• Backport of ‘Fix award emoji and note updates not reflecting live on MR page’ to 19.0 …

Help us learn about your current experience with the documentation. Take the survey.

On June 18, 2026, GitLab 19.1 was released with the following features. We’d also like to announce this month’s Notable Contributor: Pishel65! We are excited to recognize Pishel65, a Level 3 contributor with 19 merged MRs and 9 more open since joining in October 2025.

Primary features

Secret false positive detection with GitLab Duo

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation · Related Issue Secret false positive detection with the GitLab Duo Agent Platform is now generally available. Security teams spend significant time investigating secret detection findings that are incorrectly flagged as actual secrets. These false positives create alert fatigue, erode trust in scan results, and divert attention from genuine security risks. When a security scan runs, GitLab Duo automatically analyzes each critical and high severity secret detection vulnerability to determine if it is a false positive. The AI assessment appears in the vulnerability report, so you have immediate context for faster and more confident triage decisions. Key features include:
• Automatic analysis: Runs after each security scan without manual trigger.
• Manual trigger: Trigger false positive detection for individual vulnerabilities on the vulnerability details page for on-demand analysis.
• Focus on high-impact findings: Analyze only critical and high severity vulnerabilities to maximize signal-to-noise improvement.
• Contextual AI reasoning: Each assessment includes an explanation of why the finding is likely a true positive, based on code context and vulnerability characteristics.
• Confidence scoring: Each detection includes a confidence score to help teams prioritize review based on the model’s certainty.
• Seamless workflow integration: Results appear directly in the vulnerability report alongside existing severity, status, and remediation information. We welcome your feedback in issue 592861.

Always on availability mode for GitLab Duo

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation · Related Issue Administrators can now set GitLab Duo to be always on for all projects in an entire instance or top-level group. When GitLab Duo is set to always on, group, subgroup, and project owners cannot turn off GitLab Duo, giving enterprises centralized AI governance for compliance and regulated environments. This new setting is symmetrical to the existing always off setting, closing a gap where GitLab Duo could be locked off but could not be locked on. This new setting is especially valuable for organizations with autonomous divisions or subsidiaries that need to guarantee consistent AI tooling across the business. To set GitLab Duo to be always on, go the instance or top-level group GitLab Duo settings and set GitLab Duo availability to Always on.

Automatically assign Code Owners as reviewers

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue Previously, you needed to select reviewers for each merge request manually, even when a CODEOWNERS file already defined who should review each file. You can now configure a project to assign Code Owners as reviewers automatically. GitLab assigns every Code Owner that matches the changed files. This happens when a merge request is created in a ready state, or when a draft is marked ready. If you already assigned a reviewer, GitLab skips automatic assignment and keeps your choice. To turn on automatic reviewer assignment, go to Settings > Merge requests > Automatic reviewer assignment and select Automatically assign all code owners as reviewers.

Compliance framework templates (beta)

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation · Related Issue You can now create compliance frameworks from predefined templates. Previously, building a compliance framework required defining every requirement and control by hand, a repetitive process when a framework had dozens of controls. Now, when you create a new framework in the Compliance center, you can:
• Select Create from template to start from a preconfigured framework with requirements and controls already in place.
• Preview each template, customize the name, description, and color, and then apply it to your group in a single step. 19 templates are available, including ISO 27001:2022, SOC 2, FedRAMP, NIST, CIS, TISAX, and more.

Improved secret detection coverage for feature branch pipelines

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation · Related Issue In GitLab versions earlier than 19.1, you couldn’t trust a feature branch pipeline to surface every secret in your branch. A new branch scanned only the latest commit. An existing branch scanned only your most recent push. A credential leaked in an earlier commit could sit undetected, reaching shared branches or production before being flagged. Now you can catch those secrets where they’re cheapest to fix. In GitLab 19.1, secret detection scans every commit from the branch’s divergence point with the default branch to the latest commit. That means fewer secrets slip through to later stages, less time rotating exposed credentials after the fact, and consistent, predictable coverage across your branches.

Tool approval guardrails for GitLab Duo agents (beta)

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation · Related Issue Administrators can now configure tool-level approval policies for GitLab Duo agents, gating sensitive actions with human approval at the moment of execution. Previously, after an AI agent was approved for a project, it could invoke any of its tools without further review, including write and destructive operations. Now, you can define rules for groups and projects that map each tool to one of three modes:
• Allow (execute silently).
• Ask (require human approval).
• Deny (block entirely). When an AI agent calls a tool in “ask” mode, the user is prompted with an inline approval card before execution proceeds. This beta release includes Agentic Chat, IDE, and flows, and emits audit events for every approval decision.

Agentic Core

Custom and external AI feature controls

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue Administrators and top-level group Owners can now control which AI agents and flows are available within their organization. They can:
• Prevent users from creating or enabling custom agents and flows. This ensures only centrally-approved AI automation is in use.
• Restrict users from enabling agents and flows owned by projects outside the group hierarchy. This limits exposure to unapproved external content.

Custom flows YAML validation

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue The AI Catalog now validates your custom flow configuration before saving or triggering it. Previously, syntax errors and misconfigured parameters in a custom flow (for example, missing inputs or unknown tool parameters) only surfaced at runtime, after a CI job had already started. This made debugging slow and difficult. Now, when you save or update a custom flow in the AI Catalog, GitLab checks the configuration upfront and surfaces any errors directly in the UI. Valid flows are unaffected and continue to save and trigger as usual.

Pattern-based tool approval for Agentic Chat

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue This feature was removed on July 10, 2026. Previously, when Agentic Chat asked you to approve a tool invocation, you could approve it once or approve the tool call with these arguments for the remainder of the session. Different arguments would require additional approval. Workflows that repeated similar commands, such as a series of git operations, forced you through a stream of nearly identical prompts. You can now choose a third approval option, Approve all uses of this tool for session. This option approves invocations of the tool for the remainder of the session whenever the arguments match the approved pattern. Pattern-based approvals are available for Agentic Chat in the GitLab UI, GitLab Duo CLI, GitLab for VS Code, and the GitLab Duo plugin for JetBrains IDEs.

Automatic code review for new GitLab customers

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com
• Links: Documentation · Related Issue Automatic reviews in Code Review Flow are now turned on by default for new GitLab Duo trial customers on GitLab.com, so you can start getting AI-powered feedback on your merge requests from day one — without any manual setup. With a new flat pricing model, you get immediate value from smarter, faster code reviews right out of the box. If needed, you can opt out in your group settings.

Foundational flows readiness checks

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated for Government
• Links: Documentation · Related Issue GitLab Duo health checks now include foundational flows readiness checks, which verify:
• The instance-level flow execution setting is enabled.
• The instance-level foundational flows setting is enabled.
• At least one active instance runner with the gitlab--duo tag is registered and connected, and uses a Docker-compatible executor.

GPT models for Code Review Flow

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue In previous versions of GitLab, Code Review Flow supported only Anthropic Claude models. Teams that could not use Anthropic models due to contractual, policy, or procurement constraints had no way to run Code Review Flow. You can now select GPT-5.2 or GPT-5.3 Codex as the model for Code Review Flow. Top-level group Owners can switch the model for Agentic Code Review in Settings > GitLab Duo > Configure features, under GitLab Duo Agent Platform. The GPT models are hosted through the GitLab AI Gateway, so no additional configuration is required. Both models passed benchmark evaluation against the GitLab Duo code review dataset, with review quality comparable to the default Claude Sonnet 4.6 Vertex model. See the code review benchmark for results.

Model selection allowlist

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue For GitLab Duo Agentic Chat, you can now configure an allowlist of approved models, and set an organization-wide default, if you are:
• On GitLab.com, a top-level group Owner.
• On GitLab Self-Managed, an instance administrator. This gives organizations control over which models users can select when using Agentic Chat.

New event triggers for flows and external agents

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue In previous versions of GitLab, you could only run flows and external agents when the service account was mentioned, assigned, or added as a reviewer. Coordinating automation around the rest of the merge request lifecycle, or around work item creation, required external glue. You can now configure triggers for four additional events:
• Merge request ready: A user marks a draft merge request as ready for review. Previously released behind a feature flag, this event trigger is now generally available. …

Help us learn about your current experience with the documentation. Take the survey.

On June 10, 2026, we released versions 19.0.2, 18.11.5, 18.10.8 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, please visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here. For security fixes, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched. We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post.

Recommended action

We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible. When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, it means all types are affected.

Security fixes

Table of security fixes

TitleSeverity Improper Access Control issue in Group SAML Identity API impacts GitLab EEHigh Cross-site Scripting issue in Analytics Dashboard impacts GitLab EEHigh Denial of Service issue in Grape API JSON parsing middleware impacts GitLab CE/EEHigh HTML injection issue in certain group setting fields impacts GitLab EEHigh Denial of Service issue in Group Placeholder Reassignments API impacts GitLab CE/EEMedium Improper Access Control issue in Merge Requests API impacts GitLab CE/EEMedium Server-Side Request Forgery issue in Gitaly repository import impacts GitLab CE/EEMedium HTML injection issue in CI/CD Catalog impacts GitLab CE/EEMedium Improper Access Control issue in Security Inventory impacts GitLab EEMedium Authorization Bypass issue in Merge Request diff impacts GitLab CE/EELow Improper Access Control issue in Todos API impacts GitLab CE/EELow Improper Neutralization issue in Service Desk email template impacts GitLab CE/EELow

CVE-2026-6552 - Improper Access Control issue in Group SAML Identity API impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with group Owner role to take over another group member’s GitLab account due to improper authorization in the Group SAML identity management functionality. Impacted Versions: GitLab EE: all versions from 15.5 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2CVSS 8.7 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N) Thanks cyberjoker for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-10087 - Cross-site Scripting issue in Analytics Dashboard impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with developer-role permissions to execute arbitrary client-side code on behalf of a targeted user due to improper input sanitization in the Analytics Dashboard. Impacted Versions: GitLab EE: all versions from 17.1 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2CVSS 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-7250 - Denial of Service issue in Grape API JSON parsing middleware impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an unauthenticated user to cause denial of service due to improper input validation in the API request parsing middleware. Impacted Versions: GitLab CE/EE: all versions from 12.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Thanks svalkanov for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-8589 - HTML injection issue in certain group setting fields impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to add unauthorized email addresses to a targeted user’s account due to improper sanitization of user-supplied input in certain group setting fields. Impacted Versions: GitLab EE: all versions from 13.1.4 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2CVSS 7.3 (CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:N) Thanks go7f0 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-1500 - Denial of Service issue in Group Placeholder Reassignments API impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to cause denial of service due to uncontrolled resource consumption when processing a specially crafted file upload. Impacted Versions: GitLab CE/EE: all versions from 17.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) Thanks a92847865 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-6269 - Improper Access Control issue in Merge Requests API impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with developer-role permissions to modify hidden merge requests due to incorrect authorization enforcements. Impacted Versions: GitLab CE/EE: all versions from 15.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2CVSS 5.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N) Thanks rogerace for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-9204 - Server-Side Request Forgery issue in Gitaly repository import impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to read arbitrary files from the Gitaly server and access internal network resources during repository import, due to insufficient validation of secondary URLs. Impacted Versions: GitLab CE/EE: all versions from 18.10 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2CVSS 5.3 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N) Thanks AndresAIFR for reporting this vulnerability

CVE-2026-10733 - HTML injection issue in CI/CD Catalog impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an authenticated user to cause denial of service on the CI/CD Catalog page due to improper sanitization. Impacted Versions: GitLab CE/EE: all versions from 17.0 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L) This vulnerability has been discovered internally by GitLab team member Miguel Jimeno

CVE-2026-6277 - Improper Access Control issue in Security Inventory impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with Security Manager-role permissions to manage project security configuration even when the relevant feature was in a disabled state, due to incorrect authorization enforcement. Impacted Versions: GitLab EE: all versions from 13.9 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) Thanks mateuszek for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-6976 - Authorization Bypass issue in Merge Request diff impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with developer-role permissions to hide changes from merge request diff views due to improper input handling of file names. Impacted Versions: GitLab CE/EE: all versions from 15.9 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2CVSS 3.7 (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N) Thanks xorz for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-3553 - Improper Access Control issue in Todos API impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to access confidential issue details due to incorrect authorization checks. Impacted Versions: GitLab CE/EE: all versions from 12.0 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2CVSS 3.1 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks go7f0 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-9694 - Improper Neutralization issue in Service Desk email template impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions, could have allowed an unauthenticated user to impersonate the GitLab Support Bot and inject arbitrary content via a specially crafted Service Desk email reply due to improper neutralization in email template processing. Impacted Versions: GitLab CE/EE: all versions from 15.9 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2CVSS 2.6 (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N) Thanks 3nvz for reporting this vulnerability through our HackerOne bug bounty program

Bug fixes

19.0.2

• Backport: Patching deployment bigint swap for missing index
• Update VERSION files
• Backport of ‘Geo: fix container repository sync for OCI image indexes’
• Backport of ‘Fix MCP tools checkbox visibility for Premium groups’
• Backport of “Move SANDBOX_SYSTEM_DIR to /var/tmp for non-root image compatibility”
• Backport of ‘Ensure uploads.id has the correct default’ into 19-0-stable-ee
• Backport of “fix Session cancel - bypass DuoApiAuthenticator checks for browser requests”
• Backport of “Bump ruby-jwt to 2.10.3” to 19.0
• Backport of “Fix JSON::ParserError escaping safe_parse in DiscussionsDiff::HighlightCache”
• Backport of “Return false when change_position is not in correct format”
• Backport of ‘Fix agentic chat model picker showing SaaS models on self-hosted gateway’
• Update Rails Gems: Backport branch ‘update-activestorage2’ into ‘19-0-stable-ee’
• Backport of ‘Show ultimate_only agents when paid license is present’ to 19.0
• Backport: Allow composite identity SAs to bypass SAML membership lock
• Backport of ‘Allow job token basic auth for generic package upload’ to 19.0
• Backport of “Exclude invalid custom instructions from code review context”
• Update dependency oj to v3.17.3
• Backport of “Make CI cache limit per job configurable by admins”
• 19-0 Stable Bump Container Registry to v4.40.1-gitlab
• [19.0 Backport] Fix: don’t set deprecated registry threshold when maxretries is configured
• Backport the Golang upgrade 1.25.9 to 19-0

18.11.5

• Backport: Patching deployment bigint swap for missing index
• [backport] praefect: Add configurable health check ping timeout option
• Enhance DNS rebinding protection in VirtualRegistries RedirectHandler
• Backport of ‘Geo: fix container repository sync for OCI image indexes’
• Backport of ‘Fix MCP tools checkbox visibility for Premium groups’
• Backport of ‘Ensure uploads.id has the correct default’ into 18-11-stable-ee
• Backport of “Fix JSON::ParserError escaping safe_parse in DiscussionsDiff::HighlightCache”
• Backport of “Bump ruby-jwt to 2.10.3” to 18.11
• Backport of “Return false when change_position is not in correct format” …

Help us learn about your current experience with the documentation. Take the survey.

Today, we are releasing versions 18.9.8, 18.8.10, 18.7.7, 18.6.8, and 18.5.7 for GitLab Community Edition and Enterprise Edition. These versions resolve a number of regressions and bugs. This patch release does not include any security fixes. This patch release addresses a regression introduced in GitLab 18.4 where issues appeared duplicated in Epic swimlane board views — showing under both their direct parent epic and the grandparent epic — even when no filter was applied. This caused boards to become cluttered and made iteration planning unreliable for teams using nested epic hierarchies. The fix restores the intended behavior: issues appear only under their direct parent epic in unfiltered swimlane views, while the full hierarchy is still shown when a user explicitly filters by a specific parent epic. Customers affected by this issue are encouraged to upgrade to the patched version.

GitLab Community Edition and Enterprise Edition

18.9.8

• Backport of Fix swimlane problem
• Backport of Fix flaky new_project_spec CI/CD from repo URL test to 18-9
• Backport ‘Pass down DOCKER_VERSION to release env pipeline’ and ‘Remove Helm based release environment QA’ to 18-9-stable-ee
• Backport ‘Bump nginx to version 1.30.1’ to 18-9
• [18.9] Mattermost Security Updates May 13, 2026

18.8.10

• [18.8] Scope start-rails-specs changes rule to MR pipelines
• 18.8 Backport of ‘update zlib to 3.2.3’
• [Backport 18.8]Fix PG::UniqueViolation in project_daily_statistics sync trigger
• Docs backport: Add note about Agent Platform flow configurations not available until 18.11
• Backport of Fix swimlane problem
• Backport ‘Pass GIT_VERSION/DOCKER_VERSION to release env pipeline’ and ‘Remove Helm based release environment QA’ to 18-8-stable-ee
• 18.8 backport of ‘Update rack to 2.2.23’
• Backport: fix: Set sv timeout when restarting Gitaly to 18.8
• [18.8] Remove Mattermost for SLES-12.5

18.7.7

• [18.7] Update dependency oj to v3.16.15
• [18.7] GLQL advanced finder, remove project_ids
• Backport oj and oj-introspect gem updates
• Backport “CI: Update CNG mirror skip job regex”
• Backport of Fix swimlane problem
• Backport ‘Pass GIT_VERSION/DOCKER_VERSION to release env pipeline’ and ‘Remove Helm based release environment QA’ to 18-7-stable-ee
• 18.7 Backport CI: Fix the package install for zypper based distros
• [18.7] Backport Mattermost Security Updates February 23, 2026
• Backport 18-7-stable - check-packages uses Pulp

18.6.8

• Backport of Validate milestone title for group import
• Backport of ‘Remove unused retag-gdk-image CI job’
• Backport: Quarantine flaky github oauth spec
• Backport of Fix swimlane problem
• Backport ‘Pass GIT_VERSION/DOCKER_VERSION to release env pipeline’ and ‘Remove Helm based release environment QA’ to 18-6-stable-ee
• Backport Pulp migration changes to 18.6

18.5.7

• 18.5 Backport: “Add type handling for findings with locations saved as Strings”
• Backport of Fix content and content-type mismatch in files e2e test
• [Backport 18.5] Exclude Git HTTP requests from authenticated web throttle
• Backport of: Handle updated Jira API calls to permit Jira issue imports again
• Backport(18.5): Update dependency @gitlab/web-ide to ^0.0.1-dev-20251210140521
• Backport of ‘Workhorse: use upstream for DWS API requests’
• Backport of flaky import spec quarantine
• Backport of “Removes feature flag enablement for svc accounts”
• Backport 18.5 - Fix searchable dropdown race condition when typing fast
• Backport: Properly quarantine broken ci spec
• Backport of Fix swimlane problem
• Backport ‘Pass GIT_VERSION/DOCKER_VERSION to release env pipeline’ and ‘Remove Helm based release environment QA’ to 18-5-stable-ee
• 18.5 - Remove manual from SLES-12.5-release-pulp job
• Start Pulp FIPS jobs after PC FIPS jobs - 18.5
• Backport Pulp migration changes to 18.5

Important notes on upgrading

This patch includes database migrations that may impact your upgrade process.

Impact on your installation:

• Single-node instances: This patch will cause downtime during the upgrade as migrations must complete before GitLab can start.
• Multi-node instances: With proper zero-downtime upgrade procedures, this patch can be applied without downtime.

Post-deploy migrations

The following version includes post-deploy migrations that can run after the upgrade:

• 18.8.10 To learn more about the impact of upgrades on your installation, see:
• Zero-downtime upgrades for multi-node deployments
• Standard upgrades for single-node installations Note: GitLab releases have skipped 18.6.7 and 18.5.6. There are no patches with these version numbers.

Updating

To update, check out our update page.

GitLab subscriptions

Access to GitLab Premium and Ultimate features is granted by a paid subscription. Alternatively, sign up for GitLab.com to use GitLab’s own infrastructure.

Help us learn about your current experience with the documentation. Take the survey.

On May 27, 2026, we released versions 19.0.1, 18.11.4, 18.10.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, please visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here. For security fixes, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched. We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post.

Recommended Action

We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible. When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, it means all types are affected.

Security fixes

Table of security fixes

TitleSeverity Improper Access Control issue in Duo AI workflow runners impacts GitLab EEHigh Denial of Service issue in Wiki impacts GitLab CE/EEMedium Incorrect Authorization issue in GraphQL WorkItem API impacts GitLab CE/EEMedium Improper Authorization issue in Duo Workflows API impacts GitLab EEMedium Missing Authorization issue in Operations impacts GitLab EEMedium Incorrect Name Resolution issue in Pipelines impacts GitLab CE/EEMedium Incorrect Authorization issue in certain authentication endpoints impacts GitLab CE/EEMedium

CVE-2026-4868 - Improper Access Control issue in Duo AI workflow runners impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user to cause specific Duo AI workflows to run under another user’s identity due to improper user identity resolution when triggering Duo AI workflow runners. Impacted Versions: GitLab EE: all versions from 18.8 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1CVSS 8.2 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N) Thanks ahacker1 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-1402 - Denial of Service issue in Wiki impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to cause denial of service due to insufficient validation. Impacted Versions: GitLab CE/EE: all versions from 17.1 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) Thanks a92847865 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-6713 - Incorrect Authorization issue in GraphQL WorkItem API impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an unauthorized user to enumerate private projects due to incorrect authorization checks. Impacted Versions: GitLab CE/EE: all versions from 18.2 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) Thanks pollito for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-5296 - Improper Authorization issue in Duo Workflows API impacts GitLab EE

GitLab has remediated an issue that when foundational flows were enabled at the group level, could have allowed an authenticated user with developer-role permissions to bypass flow restrictions under certain conditions. Impacted Versions: GitLab EE: all versions from 18.7 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N) Thanks rogerace for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-2601 - Missing Authorization issue in Operations impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with developer-role permissions to access sensitive deployment data on projects due to improper authorization checks. Impacted Versions: GitLab EE: all versions from 11.5 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks modhanami for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-8716 - Incorrect Name Resolution issue in Pipelines impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to access CI data from a different ref type than intended. Impacted Versions: GitLab CE/EE: all versions from 12.7 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) This vulnerability has been discovered internally by GitLab team member Hordur Freyr Yngvason

CVE-2026-2710 - Incorrect Authorization issue in certain authentication endpoints impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed a blocked Project Access Token to continue accessing private resources due to incorrect authorization enforcement. Impacted Versions: GitLab CE/EE: all versions from 18.9 before 18.10.7, 18.11 before 18.11.4, and 19.0 before 19.0.1CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) Thanks s4dmach1ne for reporting this vulnerability through our HackerOne bug bounty program

Bug fixes

19.0.1

• Backport ‘Remove Helm based release environment QA’ to 19-0-stable-ee
• Backporting 19.0 final release notes
• Backport of ‘Fix broken trial CTAs on SM GitLab Credits dashboard’ into 19-0-stable-ee
• Backport API Security remediation guidance release note to 19-0-stable-ee
• Backport of ‘Add write option for Repositories in job token fine-grained permissions’ to 19.0

18.11.4

• Backport ‘Add Ruby thread scheduler priority patch’ to 18.11
• Bump GITLAB_ELASTICSEARCH_INDEXER_VERSION to 5.14.7
• Revert “backchannel: remove hashicorp yamux in favor of libp2p yamux”
• [18.11] Backport of Gate commit traversal_ids behind AddTraversalIdsToCommits migration
• Backport “Fix comments lost when moving wiki page”
• Backport of ‘Allow subgroup-provisioned SAs to create subgroups’ to 18.11
• Backport: Update Zlib to 3.2.3
• Backport of ‘Fix SyncPolicyWorker timeout on linked root namespaces’ to 18.11
• Backport of ‘Fixes dropping successful builds’
• Backport of Fixed flaky CI Catalog Resource name filter happy path spec
• Backport of Added waits to traces and cancel pipeline in after block
• Backport of ‘Add ai_workflows scope’
• Backport of Fix swimlane problem
• Backport of Fix flaky new_project_spec CI/CD from repo URL test to 18-11
• Backport of ‘Send allowed endpoints to Workhorse for diagram proxy’
• [18.11] Backport of ‘Use primary DB connection for advanced search bulk indexer’
• Backport of “Performance optimizations for the license approval rules workflow(behind FF)”
• Backport of ‘Bump gitlab-shell version to 14.50.0’
• Backport of ‘Fix off-by-one error in when num_context_lines=0’
• [18.11] Backport of ‘Fix epic boards flaky specs’
• Backport ‘Remove Helm based release environment QA’ to 18-11-stable-ee
• Backport of ‘Fix broken trial CTAs on SM GitLab Credits dashboard’ to 18.11
• Backport of ‘Gate trial CTA’s using redirect based on FF’ into 18.11
• Backport of ‘Fall back to extracting sequence name from column default’ to 18.11
• Backport ‘Update outdated test certificates’ to 18-11-stable
• Backport ‘Bump nginx to version 1.30.1’ to 18-11
• Backport ‘Add Ruby thread scheduler priority patch’ to 18.11
• [18.11] Mattermost Security Updates May 13, 2026
• [18.11] Mattermost Security Updates May 21, 2026
• Update dependency python to v3.14.4 (backport to 18-11-stable)

18.10.7

• Bump GITLAB_ELASTICSEARCH_INDEXER_VERSION to 5.14.7
• [18.10] Backport of Gate commit traversal_ids behind AddTraversalIdsToCommits migration
• 18.10 Backport of ‘update zlib to 3.2.3’
• Backport of ‘Allow subgroup-provisioned SAs to create subgroups’ to 18.10
• Backport of ‘Fix SyncPolicyWorker timeout on linked root namespaces’ to 18.10
• Backport of Fixed flaky CI Catalog Resource name filter happy path spec
• Backport of Added waits to traces and cancel pipeline in after block
• Backport of ‘Add ai_workflows scope’
• Backport of Fix swimlane problem
• Backport of Fix flaky new_project_spec CI/CD from repo URL test to 18-10
• Backport of “Performance optimizations for the license approval rules workflow(behind FF)”
• [18.10] Backport of ‘Use primary DB connection for advanced search bulk indexer’
• [18.10] Backport of ‘Fix epic boards flaky specs’
• Backport ‘Remove Helm based release environment QA’ to 18-10-stable-ee
• Backport of ‘Gate trial CTA’s using redirect based on FF’ into 18.10
• Backport of ‘Resolve: NoMethodError: undefined method `base_score’ for an instance of CvssSuite::Cvss40 (NoMethodError)’
• Backport ‘Bump nginx to version 1.30.1’ to 18-10
• [18.10] Mattermost Security Updates May 13, 2026
• Downgrade python (18.10)

Important notes on upgrading

These versions do not include any new migrations, and for multi-node deployments, should not require any downtime. Please be aware that by default the Omnibus packages will stop, run migrations, and start again, no matter how “big” or “small” the upgrade is. This behavior can be changed by adding a /etc/gitlab/skip-auto-reconfigure file, which is only used for updates.

Updating

To update GitLab, see the Update page. To update GitLab Runner, see the Updating the Runner page.

Receive Patch Notifications

To receive patch blog notifications delivered to your inbox, visit our contact us page. To receive release notifications via RSS, subscribe to our patch release RSS feed or our RSS feed for all releases.

Help us learn about your current experience with the documentation. Take the survey.

On May 21, 2026, GitLab 19.0 was released with the following features. We’d also like to announce this month’s Notable Contributor: Norman Debald! We are excited to recognize Norman, a Level 3 contributor with more than 40 merged improvements across GitLab since joining in May 2022.

Primary features

Group-level custom review instructions for GitLab Duo

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: GitLab Duo Enterprise
• Links: Documentation · Related Issue In previous versions of GitLab, you could only define custom review instructions for GitLab Duo at the project level. Teams working across many projects in the same group had to duplicate the same instructions in every project. Now you can configure shared custom review instructions for an entire group and its subgroups. Select a project in your group to use as a template. When GitLab Duo performs a code review, it combines the group-level .gitlab/duo/mr-review-instructions.yaml file with any instructions defined in the individual project. Both Code Review Flow and GitLab Duo Code Review support group-level custom instructions.

Configure work item types

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue Previously, work item types could be either an Issue or a Task. You can now configure custom work item types in a project to match the way your team plans and tracks work. You can create or rename types to User Story, Bug, or Maintenance. Each work item displays with its type name and a unique icon. The new types support custom fields and status lifecycles, and appear in your saved views and issue boards. Type configuration in the top-level group (GitLab.com) or organization (GitLab Self-Managed) cascades down to all projects. You can also control which types are available for each project. Enable or disable a type across all projects at once, or let individual projects manage their own type visibility. When you disable a type in a project, existing work items are not affected.

GitLab Secrets Manager now available in open beta

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed
• Links: Documentation · Related Issue In previous versions of GitLab, the GitLab Secrets Manager was available only to a closed beta cohort. Most teams relied on external services such as HashiCorp Vault or AWS Secrets Manager. The GitLab Secrets Manager is now available in open beta for Premium and Ultimate customers on GitLab.com and GitLab Self-Managed. When the GitLab Secrets Manager is enabled, project and group Owners can store, retrieve, and reference CI/CD secrets in GitLab. Secrets are scoped to a project or group and are accessible to only pipeline jobs that explicitly request them. During open beta, GitLab Secrets Manager follows the beta support policy and might not be ready for production use. To share feedback, see issue 598100.

GitLab Duo Developer enhancements for merge request workflows

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue GitLab Duo Developer now supports multiple trigger methods: assign it to an issue, select Generate MR, or @mention it in any issue or MR discussion thread to turn feedback, To-do items, and design questions into code changes, follow-up MRs, or research summaries. With AGENTS.md and agent-config.yml configured, GitLab Duo Developer runs your tests and checks before committing. After a top-level group or instance administrator enables the Developer Flow, GitLab automatically adds mention and assign triggers to eligible projects.

Dependency scanning by using SBOM generally available

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue The GitLab SBOM-based dependency scanner is now generally available. Maven, Gradle, and Python projects now have complete visibility into vulnerabilities across their full dependency tree, including vulnerable packages introduced transitively, not just those declared directly. The analyzer now includes automatic dependency resolution for Maven, Gradle, and Python projects. When a lockfile or resolved dependency graph is not present, the analyzer automatically invokes tooling to resolve the full transitive dependency graph before scanning. Dependency resolution is enabled by default and requires little-to-no additional configuration beyond including the v2 Dependency Scanning template. For projects where dependency resolution is not possible, the analyzer falls back to manifest scanning. It parses pom.xml, requirements.txt, build.gradle, and build.gradle.kts to identify direct dependencies. Manifest scanning ensures teams always get a starting point for vulnerability coverage, even for projects without lock or build files. Manifest scanning is enabled by default and returns direct dependencies only. For full transitive coverage, enable dependency resolution or provide a dependency lockfile or graph export manually.

Agentic Core

GitLab Duo Core moves to usage-based billing

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue Starting in GitLab 19.0, GitLab Duo Core moves to usage-based billing. Code Suggestions in the Web IDE and desktop IDEs now consume GitLab Credits. GitLab Duo Chat is also changing. For GitLab Duo Core users, Chat is now agentic and runs on GitLab Duo Agent Platform. To use GitLab Duo Chat in the GitLab UI or desktop IDEs, enable GitLab Duo Agent Platform for your instance or top-level group.

Filter exact code search results by repository

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed
• Links: Documentation · Related Issue You can now filter exact code search results by repository. With the repo: syntax, you can directly scope your search query to specific repositories or repository patterns without having to go to individual projects. For example, searching for def authenticate repo:my-group/my-project returns results only from that repository. You can also use partial paths or patterns to match multiple repositories.

Merge request ready event trigger

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed
• Links: Documentation · Related Issue You can now configure flows and external agents to run on the Merge request ready event. When a draft merge request is marked as ready for review, GitLab Duo automatically runs the flow or external agent. To configure a trigger, go to AI > Triggers in your project. This feature is behind the merge_request_ready_flow_trigger feature flag, disabled by default.

Claude Opus 4.7 now available in GitLab Duo Agent Platform

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue Claude Opus 4.7 is now available in GitLab Duo Agent Platform. Opus 4.7 delivers meaningful improvements to complex, multistep tasks that require sustained reasoning, precise instruction following, and self-verification before surfacing results. This includes flows supporting CI/CD pipelines, code review, vulnerability resolution, and more.

Support for self-hosted Gemini models

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Links: Documentation · Related Issue GitLab Duo Agent Platform Self-Hosted is now compatible with Gemini models. Gemini models support multiple flows, including the Code Review Flow, SAST Vulnerability Resolution Flow, Fix CI/CD Pipeline Flow, and more.

Expanded open source model support in GitLab Duo Agent Platform

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Links: Documentation · Related Issue GitLab Duo Agent Platform now supports additional open source models for self-hosted deployments, including Devstral 2 123B, GLM-5.1-FP8, and others. This helps customers power agentic workflows across a variety of environments, including offline and network-restricted deployments.

Per-session tool approvals with admin controls

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue Before GitLab Duo Agentic Chat can use a tool on your behalf, it requires your approval. Each tool invocation requires a separate approval. Now, you can approve a trusted tool once for an entire session and streamline your workflows. Administrators control whether tool approval for sessions is available. The following settings cascade from instance to group to project:
• On by default
• Off by default
• Always off Groups and subgroups can modify the setting unless an administrator sets it to Always off. The default setting is Off by default, ensuring each tool invocation requires explicit approval unless an administrator changes it.

Resolve merge conflicts with GitLab Duo (Beta)

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue In previous versions of GitLab, you had to resolve merge conflicts manually in the GitLab UI or from the command line, even for straightforward cases. Now GitLab Duo can autonomously analyze merge conflicts, edit the conflicting files, create a commit, and push to the source branch. Trigger conflict resolution from the Resolve conflicts page or directly from the merge request widget. When complete, GitLab Duo posts a summary comment so reviewers can see what changed. GitLab Duo respects branch protection rules and does not force-push to protected branches. This feature is in beta and is gated behind the mr_ai_resolve_conflicts feature flag, enabled by default.

Restrict the AI Catalog to a group hierarchy

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue Top-level group Owners can now restrict the AI Catalog to show only agents and flows owned by projects within their group hierarchy. This blocks agents, external agents, or flows not in this hierarchy from being visible or enabled by any user in that group.

Purchase credits on the Free tier on GitLab Self-Managed

• Tier: Free
• Offering: GitLab Self-Managed
• Links: Documentation · Related Issue Free tier users on GitLab Self-Managed can now unlock the full power of GitLab Duo Agent Platform, no Premium or Ultimate subscription required. Choose your monthly credit amount, commit to an annual term, and get instant access to AI-powered development tools. Credits refresh automatically each month, so your team always has what it needs to build faster and smarter.

Admin-defined network access controls for Agent Platform remote flows

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation · Related Issue Administrators can now define centralized network policies for GitLab Duo Agent Platform remote flows directly in Settings. Top-level group administrators on GitLab.com, and instance administrators on GitLab Self-Managed and Dedicated, can configure organization-wide domain denylists and allowlists that projects inherit automatically. An additional setting controls whether projects can extend the approved domain list with custom entries. Policies are enforced at runtime across all remote flows, giving security and platform teams a consistent governance layer for agent network egress.

Unified DevOps and Security

Auto remediation for vulnerable dependencies (Experiment)

• Tier: Ultimate
• Offering: GitLab.com
• Links: Documentation · Related Issue …

Help us learn about your current experience with the documentation. Take the survey.

On May 13, 2026, we released versions 18.11.3, 18.10.6, 18.9.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important bug and security fixes, and we strongly recommend that all self-managed GitLab installations be upgraded to one of these versions immediately. GitLab.com is already running the patched version. GitLab Dedicated customers do not need to take action. GitLab releases fixes for vulnerabilities in patch releases. There are two types of patch releases: scheduled releases and ad-hoc critical patches for high-severity vulnerabilities. Scheduled releases are released twice a month on the second and fourth Wednesdays. For more information, please visit our releases handbook and security FAQ. You can see all of GitLab release blog posts here. For security fixes, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched. We are committed to ensuring that all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standards. To maintain good security hygiene, it is highly recommended that all customers upgrade to the latest patch release for their supported version. You can read more best practices in securing your GitLab instance in our blog post.

Recommended Action

We strongly recommend that all installations running a version affected by the issues described below are upgraded to the latest version as soon as possible. When no specific deployment type (omnibus, source code, helm chart, etc.) of a product is mentioned, it means all types are affected.

Security fixes

Table of security fixes

TitleSeverity Cross-site Scripting issue in Analytics dashboard chart rendering impacts GitLab EEHigh Cross-site Scripting issue in global search impacts GitLab CE/EEHigh Cross-site Scripting issue in Duo Agent output rendering impacts GitLab EEHigh Cross-site Scripting issue in Analytics Dashboard impacts GitLab EEHigh Denial of Service issue in CI/CD job update API impacts GitLab CE/EEHigh Denial of Service issue in Duo Workflows API impacts GitLab CE/EEHigh Denial of Service issue in internal API endpoints impacts GitLab CE/EEHigh Improper Authorization issue in GraphQL token scope enforcement impacts GitLab CE/EEMedium Denial of Service issue in Insights Configuration impacts GitLab EEMedium Access Control issue in Issues API impacts GitLab CE/EEMedium Denial of Service issue in direct transfer CSV parser impacts GitLab CE/EEMedium CSRF issue in JiraConnect subscriptions impacts GitLab CE/EEMedium Confused Deputy issue in Jira integration impacts GitLab CE/EEMedium Cross-site Scripting issue in Banzai markdown sanitizer impacts GitLab CE/EEMedium Cross-site Scripting issue in achievement email notifications impacts GitLab CE/EEMedium Access Control issue in Helm package upload impacts GitLab CE/EEMedium Improper Access Control issue in NuGet Symbol Server impacts GitLab CE/EEMedium Improper Access Control issue in Container Registry protected tags impacts GitLab CE/EEMedium Missing Authorization issue in group user search impacts GitLab CE/EEMedium Improper Access Control issue in code owner approval rules impacts GitLab EEMedium Access Control issue in PyPI Package Protection Rules impacts GitLab CE/EEMedium Improper Access Control issue in issue links API impacts GitLab CE/EEMedium Server-Side Request Forgery issue in virtual registry redirect handler impacts GitLab EELow Access Control issue in GraphQL approval rule mutations impacts GitLab EELow Missing Authorization issue in Security Policy Project Reassignment impacts GitLab EELow

CVE-2026-7481 - Cross-site Scripting issue in Analytics dashboard chart rendering impacts GitLab EE

GitLab has remediated an issue that could have allowed an authenticated user with developer-role permissions to execute arbitrary JavaScript in other users’ browsers due to improper input sanitization. Impacted Versions: GitLab EE: all versions from 16.4 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3CVSS 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) Thanks yvvdwf for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-5297 - Cross-site Scripting issue in global search impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an authenticated user to execute arbitrary JavaScript in other users’ browsers due to improper input sanitization. Impacted Versions: GitLab CE/EE: all versions from 15.11 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3CVSS 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) This vulnerability has been discovered internally by GitLab team member Chaoyue Zhao and special thanks to a_m_a_m for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-6073 - Cross-site Scripting issue in Duo Agent output rendering impacts GitLab EE

GitLab has remediated an issue that could have allowed an authenticated user to execute arbitrary JavaScript in other users’ browsers due to improper input sanitization. Impacted Versions: GitLab EE: all versions from 18.7 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3CVSS 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-7377 - Cross-site Scripting issue in Analytics Dashboard impacts GitLab EE

GitLab has remediated an issue that, in customizable analytics dashboards, could have allowed an authenticated user to execute arbitrary JavaScript in the context of other users’ browsers due to improper input sanitization. Impacted Versions: GitLab EE: all versions from 18.7 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3CVSS 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N) Thanks aphantom for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-1659 - Denial of Service issue in CI/CD job update API impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an unauthenticated user to cause denial of service by sending specially crafted requests due to insufficient input validation. Impacted Versions: GitLab CE/EE: all versions from 9.0 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Thanks a92847865 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2025-14870 - Denial of Service issue in Duo Workflows API impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an unauthenticated user to cause denial of service by sending specially crafted JSON payloads due to insufficient input validation. Impacted Versions: GitLab CE/EE: all versions from 18.5 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Thanks a92847865 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2025-14869 - Denial of Service issue in internal API endpoints impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an unauthenticated user to cause denial of service by sending specially crafted payloads on certain API endpoints. Impacted Versions: GitLab CE/EE: all versions from 18.5 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Thanks a92847865 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-1322 - Improper Authorization issue in GraphQL token scope enforcement impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an authenticated user with a read_api scoped OAuth application to create issues and add comments to issues in private projects due to improper authorization. Impacted Versions: GitLab CE/EE: all versions from 16.0 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3CVSS 6.8 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N) Thanks mateuszek for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-1184 - Denial of Service issue in Insights Configuration impacts GitLab EE

GitLab has remediated an issue that could have allowed an unauthenticated user to cause denial of service by uploading a specially crafted file due to improper validation. Impacted Versions: GitLab EE: all versions from 11.9 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) Thanks a92847865 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-4524 - Access Control issue in Issues API impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an authenticated user to access confidential issue content in public projects without proper authorization due to improper authorization checks. Impacted Versions: GitLab CE/EE: all versions from 18.9.1 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) Thanks hackaccinocraft for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-8280 - Denial of Service issue in direct transfer CSV parser impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an authenticated user to cause denial of service through excessive memory consumption due to improper input validation. Impacted Versions: GitLab CE/EE: all versions from 8.3 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H) Thanks a92847865 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-4527 - CSRF issue in JiraConnect subscriptions impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an unauthenticated user to create unauthorized Jira subscriptions for a targeted user’s namespace via a specially crafted link due to missing CSRF protection. Impacted Versions: GitLab CE/EE: all versions from 11.10 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3CVSS 6.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) Thanks maksyche for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-3160 - Confused Deputy issue in Jira integration impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an authenticated user to view Jira issues outside the configured project scope due to an integration filter functioning only as a display control rather than enforcing access boundaries as specified. Impacted Versions: GitLab CE/EE: all versions from 13.7 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3CVSS 5.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N) Thanks maksyche for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-6335 - Cross-site Scripting issue in Banzai markdown sanitizer impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to execute arbitrary code in another user’s browser session due to improper sanitization. Impacted Versions: GitLab CE/EE: all versions from 18.11 before 18.11.3CVSS 5.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) Thanks toofikz for reporting this vulnerability through our HackerOne bug bounty program

CVE-2025-12669 - Cross-site Scripting issue in achievement email notifications impacts GitLab CE/EE

GitLab has remediated an issue that could have allowed an authenticated user to inject HTML and JavaScript into email notifications sent to other users due to improper input sanitization. Impacted Versions: GitLab CE/EE: all versions from 15.11 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3CVSS 5.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N) …

Help us learn about your current experience with the documentation. Take the survey.

On April 29, 2026, we released versions 18.11.2 and 18.10.5 for GitLab Community Edition and Enterprise Edition. These out-of-band patch releases fix an observability gap to ensure we continue to meet our disaster recovery RTO/RPO commitments for our GitLab Dedicated customers. These versions also resolve a number of regressions and bugs. This patch release does not include any security fixes.

GitLab Community Edition and Enterprise Edition

18.11.2

• Revert “Merge branch ‘ia-refactor-role-permission-enablement’ into ‘master’”
• ‘Add Code Suggestion to the DAP supported features for self-hosted models’
• ‘Clear persisted filters when loading /work_items page’
• ‘Allow Duo Core user to still use DAP code review’
• ‘GraphQL mutation to retry failed reassigments’ into 18.11
• “Resolve sidekiq spikes when a User is banned”
• Fix MCP OAuth discovery failing on relative URL installs
• ’*_oldest_unsynced_time’ metric addition

18.10.5

• ‘Add Code Suggestion to the DAP supported features for self-hosted models’
• “Update Duo CLI version for remote flows”
• “BBM - Skip 3 migrations referencing dropped tables”
• ‘Allow Duo Core user to still use DAP code review’
• “Resolve sidekiq spikes when a User is banned”
• ‘Fix: self-hosted feature setting missing model_definitions’
• “fix: Skip CreateOrUpdateDefaultTrackedContextWorker on Geo secondaries”
• ’*_oldest_unsynced_time’ metric addition

Important notes on upgrading

This patch includes database migrations that may impact your upgrade process.

Impact on your installation:

• Single-node instances: This patch will cause downtime during the upgrade as migrations must complete before GitLab can start.
• Multi-node instances: With proper zero-downtime upgrade procedures, this patch can be applied without downtime.

Regular migrations

The following version includes regular migrations that run during the upgrade process:

• 18.10.5

Post-deploy migrations

The following version includes post-deploy migrations that can run after the upgrade:

• 18.11.2
• 18.10.5 To learn more about the impact of upgrades on your installation, see:
• Zero-downtime upgrades for multi-node deployments
• Standard upgrades for single-node installations

Updating

To update, check out our update page.

GitLab subscriptions

Access to GitLab Premium and Ultimate features is granted by a paid subscription. Alternatively, sign up for GitLab.com to use GitLab’s own infrastructure.

Help us learn about your current experience with the documentation. Take the survey.

On April 16, 2026, GitLab 18.11 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor.

This month’s Notable Contributor: Rinku C

We are excited to recognize Rinku C, a Level 4 contributor with over 80 merged improvements across GitLab since joining in September 2025. Nominated by Arianna Haradon, Senior Fullstack Engineer on the Developer Relations team, this award celebrates his sustained and meaningful impact over time. Rinku has strengthened security-sensitive flows by requiring scopes on project and group access token creation forms, and improved everyday GitLab experience with numerous updates like next/previous navigation in job logs, excluding empty searches from recent, and reducing file tree clutter through thoughtful UI refinements that make common workflows clearer and easier to navigate. Rinku tackles the work that often goes unclaimed, keeping the codebase healthy and compounding to meaningful, lasting value. Thank you for your contributions!

Primary features

Vulnerability resolution generally available on GitLab Duo Agent Platform

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue Agentic SAST Vulnerability Resolution is now generally available in GitLab 18.11 on the GitLab Duo Agent Platform. It runs as part of your SAST scan, after SAST false positive detection runs, or when manually triggered for individual SAST vulnerabilities. Agentic SAST Vulnerability Resolution:
• Autonomously analyzes the finding and reasons through the surrounding code context.
• Automatically creates a ready-to-review merge request with proposed code fixes for critical and high severity SAST vulnerabilities.
• Provides quality assessments so reviewers can quickly gauge confidence in the proposed remediation.
• Allows you to apply resolutions directly from vulnerability details pages. We welcome your feedback in issue 585626.

GitLab Data Analyst Foundational Agent now generally available

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic The Data Analyst Agent is a specialized AI chat assistant that helps you query, visualize, and surface data across the GitLab platform. Backed by the GitLab Query Language (GLQL), the Data Analyst can retrieve and analyze data about each of the supported data sources, and provide clear, actionable insights about your software development health and engineering efficiency. These insights can be visualized directly in the agent output and embedded directly into issues and epics for further evaluation.

CI Expert Agent launches in beta

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related issue The AI-powered CI Expert Agent is now available in beta. This agent helps teams get from GitLab code to a first working pipeline without starting from a blank .gitlab-ci.yml. Using GitLab Duo Agent Platform, the agent inspects your repository, asks a few guided questions about your build and test process, and generates a ready-to-run pipeline you can review, edit, and commit. This turns pipeline creation into a conversational, context-aware experience, while still letting you take full control of the YAML after you’re ready to evolve and optimize your configuration.

Automated vulnerability severity overrides

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic Default vulnerability severities don’t always reflect your organization’s actual risk. A critical CVE in an internal-only service might not warrant the same urgency as one in a public-facing application, yet teams spend significant time triaging findings that don’t match their risk model. Vulnerability management policies can now automatically adjust the severity of vulnerabilities based on conditions like CVE ID, CWE ID, file path, and directory. When applied, the policy updates the severity of any vulnerability that matches the criteria on the default branch. Manual overrides still take precedence, and all changes are logged in the vulnerability’s history and audit events. This reduces triage work and ensures developers focus on the findings that matter most to your business.

Create Service Account in subgroups and projects

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic Teams can now create service accounts in subgroups and projects. Instead of broad, top-level group bots, you can attach a dedicated service account to a single subgroup or project and manage its access like any other member of that namespace. Group and subgroup service accounts can be invited to the group where they were created or to any descendant subgroups and projects. Project service accounts are limited to their own project.

Service Accounts available on GitLab Free

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic Service accounts are now available on GitLab.com in all tiers. Previously limited to Premium and Ultimate, service accounts let you perform automated actions, access data, or run scheduled processes without tying credentials to individual team members. They’re commonly used in pipelines and third-party integrations where credentials must stay stable regardless of team changes. On GitLab Free, you can create up to 100 service accounts per top-level group, including those created in subgroups or projects.

Fine-grained permissions for personal access tokens now available (Beta)

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic Fine-grained personal access tokens (PATs) are now available in beta. Unlike legacy PATs, which grant access to every project and group you belong to, fine-grained PATs let you limit each token to specific resources and actions. This reduces the potential impact of a leaked or compromised token. Your existing PATs continue to work as before, and you can still create legacy PATs without fine-grained permissions. This beta release covers approximately 75% of the GitLab REST API. Full REST API coverage, GraphQL enforcement, and administrator policy controls are planned for the GA release. To share feedback, see epic 18555.

Top CWE chart in security dashboards

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic The top CWE chart is now available on the new security dashboards. Identify the most common CWEs across your project or instance to identify opportunities for training, improvement, or program optimization. Users can group the dashboard data by severity and filter the dashboard by severity, project, and report type.

Deploy Gitaly on Kubernetes

• Tier: Free, Premium, Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related issue You can now deploy Gitaly on Kubernetes as a fully supported deployment method. This gives you greater flexibility in managing your GitLab infrastructure by using Kubernetes orchestration capabilities for scaling, high availability, and resource management. Previously, Kubernetes deployments required custom configurations and weren’t officially supported, making it difficult to maintain reliable Gitaly deployments in containerized environments.

Reconfigure inputs when manually running MR pipelines

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related issue A powerful aspect of CI/CD inputs is that you can manually run new pipelines with new values for runtime customization. This was not available in merge request (MR) pipelines before, but in this release you can now customize inputs in MR pipelines too. After you configure inputs for MR pipelines, you can optionally modify those inputs and change the pipeline behavior any time you run a new pipeline for a merge request.

Agentic Core

Default model for GitLab Duo Agentic Chat updated from Haiku 4.5 to Sonnet 4.6

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue We’ve made an update to improve your Agentic Chat experience in GitLab. The default model for Agentic Chat was upgraded from Claude Haiku 4.5 to Claude Sonnet 4.6, hosted on Vertex AI. Claude Sonnet 4.6 offers improved reasoning and response quality but uses a higher GitLab Credit multiplier than Haiku 4.5. You can select an alternative model, including Haiku, using the model selection setting. If you’ve already selected a specific model, your choice is preserved. This update only affects the default and will not override any existing selections. For information about credit multipliers by model, see the GitLab Credits documentation.

Configure tools in custom flow definitions

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related issue You can now configure tool options and parameter values directly in your custom flow definitions to supersede the LLM default values. This gives you more precise, consistent control over how tools behave within a custom flow, making it easier to enforce guardrails and specific parameter values across that flow.

Mistral AI now supported as a self-hosted model in GitLab Duo Agent Platform

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Links: Documentation | Related issue GitLab Duo Agent Platform now supports Mistral AI as an LLM platform for self-hosted model deployments. GitLab Self-Managed customers can configure Mistral AI alongside existing supported platforms, including AWS Bedrock, Google Vertex AI, Azure OpenAI, Anthropic, and OpenAI. This gives teams more choice in how they run AI-powered features.

Scale and Deployments

View historical months in GitLab Credits dashboard

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related issue The GitLab Credits dashboard in Customers Portal now supports historical month navigation. Billing managers can browse past billing months to review daily usage trends, compare consumption patterns across periods, and reconcile usage with invoices. Previously, the dashboard only displayed the current billing month. With this improvement, administrators can make more informed decisions about credit allocation and forecast future needs based on historical data.

Set subscription-level usage cap for GitLab Credits

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation …

Help us learn about your current experience with the documentation. Take the survey.

On March 19, 2026, GitLab 18.10 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor.

This month’s Notable Contributor: Harshith Sudar

Harshith is currently a Level 3 Contributor who has made impactful contributions improving community tooling and analytics, from triage automation and contributor recognition to GitLab Duo usage insights. Harshith’s contributions were first recognized by Lee Tickett, Fullstack Engineer in DevRel Engineering at GitLab, who nominated him. His work has strengthened how we support contributors behind the scenes through improvements to our automation and contributor-facing experiences. For example, he expanded our triage automation by updating the IssueSummary processor in triage-ops to work with multiple projects, including contributors.gitlab.com, making it easier for us to keep more community projects consistently summarized and visible. He also helped recognize community-created content through the new “Add content” button and flow, which lets contributors log blog posts, videos, and other content directly from their profile and get rewarded. Harshith has also contributed to our analytics and GitLab Duo usage insights. Highlights include refining how GitLab Duo usage is calculated, improving how AI impact over time can be explored by removing the 180-day default, and consolidating DORA metric date range constants, as well as enhancing analytics at scale with improvements like adding infinite scroll for the Value Stream Analytics custom stage label picker. Together, these changes help teams better understand how GitLab is used in real projects. In his own words: “One thing I’ve really enjoyed while contributing is how thoughtfully ideas are discussed within the community. It’s encouraging to see suggestions explored collaboratively, like in the discussion around MR !1288, which turned into a great learning experience. I’m really happy to be part of this community and look forward to making many more contributions in the future.” Thank you, Harshith, for your ongoing work to improve the GitLab codebase and contributor experience! Want to connect with Harshith and learn more about his contributions? Visit Harshith’s GitLab profile and his LinkedIn profile.

Primary features

SAST false positive detection with GitLab Duo Agent Platform

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Core, Duo Pro, Duo Enterprise
• Links: Documentation | Related epic SAST false positive detection, which was first introduced as a beta in GitLab 18.7, is now generally available in GitLab 18.10. When a security scan runs, GitLab Duo Agent Platform analyzes each critical and high severity SAST vulnerability and determines the likelihood that it’s a false positive. The assessment appears directly in the vulnerability report, giving teams the context they need to triage with confidence rather than uncertainty. Key capabilities include:
• Automatic analysis: False positive detection runs automatically after each security scan with no manual intervention required.
• Manual option: Users can manually run false positive detection for individual vulnerabilities on the vulnerability details page for on-demand analysis.
• Focus on high-impact findings: Limiting the analysis to critical and high severity SAST vulnerabilities cuts through the noise where it matters most.
• Contextual AI reasoning: Each assessment explains why a finding may or may not be a false positive, factoring in code context, data flow, and vulnerability characteristics specific to static analysis.
• Seamless workflow integration: Results surface directly in the vulnerability report alongside existing severity, status, and remediation information — no changes to existing workflows required. This feature is available for Ultimate customers with GitLab Duo Agent Platform. The feature must be enabled in your group or project settings. We welcome your feedback in issue 583697.

Purchase GitLab Credits on the Free tier on GitLab.com

• Tier: Free
• Offering: GitLab.com
• Add-ons: GitLab Credits
• Links: Documentation | Related epic Free tier group Owners on GitLab.com can now unlock AI with GitLab Credits. Purchase a monthly credit amount, commit to an annual term, and get access to GitLab Duo Agent Platform agents and flows. Credits refresh automatically each month, so your team always has what it needs to build faster and smarter. Key highlights:
• Usage-based pricing: Purchase a monthly credit commitment without needing a base plan subscription.
• Self-service purchasing: Buy credits through the GitLab purchase flow.
• Seamless upgrade path: Your credit commitment transfers if you later upgrade to Premium or Ultimate.
• Consumption tracking: Monitor your credit usage through the GitLab Credits dashboard. This purchase option is currently only available for free GitLab.com top-level groups.

Sign in securely with passkeys

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic GitLab now supports passkeys for passwordless sign-in and as a phishing-resistant two-factor authentication (2FA) method. Passkeys use public-key cryptography and biometric authentication (fingerprint, face recognition) or your device PIN to securely access your account. Passkeys offer the following benefits:
• Passwordless convenience: Sign in with your device’s biometrics or PIN instead of remembering a password.
• Multi-device support: Use passkeys on desktop browsers, mobile devices (iOS 16 or later, Android 9 or later), and FIDO2/WebAuthn-compatible hardware security keys.
• Phishing-resistant security: Your private key never leaves your device. GitLab only stores the public key, protecting your account even if GitLab servers are compromised.
• Automatic 2FA integration: For accounts with 2FA enabled, passkeys become available as your default 2FA method. To get started, add a passkey in your account settings. We welcome your questions and feedback in issue 366758.

Introducing the work items list and saved views

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic The GitLab planning experience is getting a significant upgrade with the work items list and saved views, bringing together two long-requested capabilities:
• The work items list combines epics, issues, and other work items into a single unified list, eliminating the need to switch between separate pages for different work item types. This makes it easier to understand relationships across your planning objects.
• Saved views allow you to create and save customized list configurations, including filters, sort order, and display options. This makes routine checks more efficient, and supports standardized ways of viewing work across your team. This is the next step in the GitLab work items journey, a unified architecture designed to deliver consistency and unlock new capabilities across GitLab planning tools. Share your thoughts and feedback in issue 590689.

Custom agents can use MCP to access external data

• Tier: Premium, Ultimate
• Offering: GitLab.com
• Links: Documentation | Related issue You can now connect custom agents in the AI Catalog to external data sources and tools through the Model Context Protocol (MCP), without leaving GitLab. This feature is an experiment. Share your feedback in issue 593219.

Enforce merge request title naming conventions with regex

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic Maintaining consistent merge request titles is important for teams that rely on structured naming conventions. Whether that’s following the Conventional Commits format, or linking to an internal tracking system. Teams previously needed external tooling or custom CI/CD pipeline jobs to enforce these conventions, but this approach had a critical gap. If someone changed the merge request title after the pipeline ran, there was no re-validation, and the MR could still be merged with a non-compliant title. You can now configure a required title regex for merge requests in your project settings. When configured, GitLab evaluates the merge request title against the pattern as a mergeability check — blocking the merge until the title is updated to comply, regardless of when the title was last changed. To set this up, go to your project’s Settings > Merge requests and enter a regex pattern in the Merge request title must match regex field. Your existing merge request workflows continue to work as before. This check only applies to projects where you explicitly configure a title regex.

Secret false positive detection with AI (beta)

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Core, Duo Pro, Duo Enterprise
• Links: Documentation | Related epic Security teams spend significant time investigating secret detection findings that turn out to be false positives. For example, test credentials, example values, and placeholder tokens that are incorrectly flagged as actual secrets. False positives create alert fatigue, erode trust in scan results, and divert attention from genuine security risks. GitLab 18.10 introduces AI-powered secret false positive detection (beta) to focus on the secrets that actually matter. When a security scan runs, GitLab Duo automatically analyzes each Critical and High severity secret detection vulnerability to determine if it’s a false positive. The AI assessment appears directly in the vulnerability report, giving security engineers immediate context to make faster and confident triage decisions. Key capabilities include:
• Automatic analysis: False positive detection runs automatically after each security scan without manual trigger.
• Manual trigger option: You can manually trigger false positive detection for individual vulnerabilities on the vulnerability details page for on-demand analysis.
• Focus on high-impact findings: Scoped for Critical and High severity vulnerabilities to maximize signal-to-noise improvement.
• Contextual AI reasoning: Each assessment includes an explanation of why the finding may or may not be a true positive, based on code context and vulnerability characteristics.
• Confidence scoring: Each detection includes a confidence score to help teams prioritize review based on the model’s certainty.
• Seamless workflow integration: Results surface directly in the vulnerability report alongside existing severity, status, and remediation information. This feature is available as a free beta for Ultimate customers and must be enabled in your group or project settings. Share feedback in issue 592861.

Use runtime inputs with CI/CD jobs

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic Using CI/CD variables for dynamic job configuration can be challenging. Variables follow a complex override hierarchy that’s difficult to manage, and they can’t be used for a variety of use cases. Now you can use inputs to define explicit, typed inputs at the job level. Use job inputs to define and control the values that a job accepts at runtime. With job inputs, you get:
• Type safety (string, number, boolean, array).
• Default values that can be static or reference existing variables.
• The option to define a strict list of possible values to use.
• Regex support for validating input values. …

Help us learn about your current experience with the documentation. Take the survey.

On February 19, 2026, GitLab 18.9 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor.

This month’s Notable Contributor: Pooja Ghanghas

Pooja has made significant contributions to ongoing efforts at GitLab to migrate legacy dropdown components to our modern dropdown architecture. These migrations require careful attention to detail and an understanding of both the old and new component systems. Pooja has consistently delivered high-quality work across multiple migrations, including updates to the diff file header, code block bubble menu, oncall schedules rotation assignee component, and the new resource dropdown. Peter Hegman, Staff Frontend Engineer on Tenant Scale::Organizations at GitLab, nominated Pooja for this recognition, noting: “These migrations can be pretty tricky and she has completed a number of them. Thanks for your contributions!” Beyond these migration efforts, Pooja has also contributed to feature development, including adding statuses to milestones and iterations, a feature she put significant effort into getting merged. Marc Saleiko, Staff Fullstack Engineer on Plan:Project Management at GitLab, recognised her work: “This is a valuable contribution and you did a great job delivering this functionality!” Reflecting on her experience, Pooja shared: “I’m proud of how it turned out and it was a great learning experience for me.” She has also contributed numerous bug fixes and maintenance improvements across the GitLab codebase. Pooja’s work directly improves the maintainability and consistency of the GitLab user interface, making it easier for both contributors and team members to build and maintain features, and helping move the GitLab frontend architecture forward. Thank you, Pooja, for your continued contributions to improving the GitLab codebase and for being such a reliable member of our contributor community! Want to learn more about Pooja’s contributions? Check out her GitLab profile.

Primary features

GitLab Duo Agent Platform Self-Hosted models now available for cloud licenses

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Links: Documentation | Related epic GitLab Duo Agent Platform is now generally available for GitLab Self-Managed customers with a cloud license. Billing for this feature is usage-based. Administrators can configure compatible models for use with GitLab Duo Agent Platform. Administrators using AWS Bedrock or Azure OpenAI can also configure Anthropic Claude or OpenAI GPT models. Not yet on Ultimate? Start a free trial with Duo Agent Platform included.

Vulnerability resolution with GitLab Duo Agent Platform (Beta)

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic Triaging and remediating SAST vulnerabilities is one of the most time-consuming tasks in application security. After identifying a real vulnerability, developers need to understand the finding, locate the affected code, and write an appropriate fix. All of which take time and specialized knowledge. In GitLab 18.9, we’re introducing Agentic SAST Vulnerability Resolution. When you trigger resolution for a SAST vulnerability, GitLab Duo autonomously analyzes the finding, reasons through the surrounding code context, generates a context-aware fix, and creates a merge request without any manual intervention. Key capabilities include:
• Agentic multi-step resolution: Rather than producing a single code suggestion, the GitLab Duo Agent Platform reasons through the vulnerability, evaluates the codebase, and produces a well-informed fix.
• Automatic merge request creation: Generates a ready-to-review merge request with the proposed code fix for critical and high severity SAST vulnerabilities.
• Quality scoring: Each generated fix includes a quality assessment so reviewers can quickly gauge confidence in the proposed remediation. SAST vulnerability resolution is available from the vulnerability report and the individual vulnerability details pages. You can trigger a resolution directly from the individual vulnerability details page. This feature is available as a free beta for Ultimate customers. We welcome your feedback in issue 585626.

Navigate repositories with collapsible file tree

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic You can now browse repository files with a collapsible file tree. The tree provides a comprehensive view of your project structure, so you can expand and collapse directories inline, jump between files in different parts of your repository, and maintain context while you work. The file tree appears as a resizable sidebar when you view repository files or directories. You can toggle visibility with keyboard shortcuts, filter files by name or extension, and navigate through complex project hierarchies. The tree synchronizes with your current location, so when you select a file in the main content area, the tree updates to show that file. Your existing repository structure and file organization remain unchanged. With fewer page loads required to move between files, this feature scales from small projects to large codebases with thousands of files.

Include CI/CD inputs from a file

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related issue Previously, pipeline inputs could only be defined directly within a pipeline’s spec section. This limitation made it challenging to reuse input configuration across multiple projects. In this release you can now include input definitions from external files using the familiar include keyword. Being able to maintain a list of inputs in a separate place helps you have a manageable solution across many projects or pipelines. You can maintain centralized input configurations and even dynamically manage input values from external sources.

Web-based commit signing on GitLab.com

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com
• Links: Documentation | Related epic Ensuring commits are cryptographically signed is essential for code integrity and meeting compliance requirements. Previously, web-based commit signing was only available for GitLab Self-Managed. GitLab.com now supports web-based commit signing. When enabled for a group or project, commits created through the GitLab web interface are automatically signed with the GitLab signing key and are displayed with a Verified badge, providing cryptographic proof of authenticity for your repositories. Key details:
• Enable in group or project settings based on your requirements.
• All web-based commits (Web IDE edits, merges, API operations) are automatically signed when enabled. This brings the GitLab.com security capabilities in line with GitLab Self-Managed and provides the foundation for comprehensive commit signing policies across your organization.

Container virtual registry now available (Beta)

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed
• Links: Documentation | Related epic Modern container-based development requires accessing images from multiple registries including Docker Hub, Harbor, Quay, and private registries. Without a container virtual registry, platform engineers must configure each project and CI/CD pipeline to authenticate with and pull from multiple registries individually. This creates configuration complexity, slows pulls with sequential registry queries, and makes it difficult to implement consistent security policies across container sources. The container virtual registry addresses these challenges by aggregating multiple upstream container registries behind a single endpoint. Platform engineers can configure Docker Hub, Harbor, Quay, and other registries with long-lived token authentication through one URL. Intelligent caching improves pull performance while integrating with the GitLab authentication systems for centralized access control and audit logging. The container virtual registry API is currently available in beta for GitLab Premium and Ultimate customers. Beta participants can use the GitLab API to create container virtual registries, configure multiple upstream sources with shareable configurations, and pull container images through the virtual registry. Please note the beta does not support registries that require IAM authentication. Support for cloud provider registries requiring IAM authentication is tracked in this epic. On GitLab.com, this feature is behind a feature flag. To request access or share feedback, please comment in the feedback issue.

New security dashboard chart: Vulnerabilities by age

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic The new Vulnerabilities by age chart helps you understand how long vulnerabilities have been open in your environment. The chart shows the distribution of unresolved vulnerabilities based on the amount of time since they were first detected. You can group vulnerabilities by severity or by report type, helping you identify where remediation activities may be needed.

Agentic Core

OAuth support in JetBrains IDEs for Self-Managed and Dedicated

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Add-ons: Duo Core, Duo Pro, Duo Enterprise
• Links: Documentation | Related issue The GitLab Duo plugin for JetBrains IDEs now supports OAuth authentication for GitLab Self-Managed and GitLab Dedicated. This means all JetBrains users can now enjoy a faster, more secure sign-in experience. No personal access token required.

Scale and Deployments

Non-billable Minimal Access users

• Tier: Premium
• Offering: GitLab Self-Managed
• Links: Documentation | Related issue Previously, organizations that used identity providers to automate user provisioning on GitLab Self-Managed Premium might run into a potential problem. When identity provider syncs attempt to add users beyond the licensed seat limit, administrators must either purchase extra seats for users who don’t need active access, or manually intervene to prevent failures. Now, users with the Minimal Access role on GitLab Self-Managed Premium subscriptions no longer count as billable seats, bringing them in line with how minimal access works on GitLab.com Premium, GitLab.com Ultimate, and GitLab Self-Managed Ultimate. This change unlocks the restricted access feature, which automatically assigns the Minimal Access role to users who would otherwise exceed the seat limit during identity provider syncs. This change keeps syncs running smoothly without unexpected billing overages or manual intervention.

Geo data management view on primary site

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated
• Links: Documentation You can now troubleshoot and verify data integrity directly from the primary site, thanks to the new data management view that brings detailed verification status information to the primary Geo site. This enhancement eliminates the need to access secondary sites for basic verification and troubleshooting tasks. Previously, this verification status was only accessible through the secondary site UI. Now, with the data management view on the primary site, you can:
• View detailed verification status for all replicable data types on the primary site
• Perform data sanitization and troubleshooting tasks directly from the primary UI
• Set up and verify your Geo configuration on the primary site before adding secondary sites …

Help us learn about your current experience with the documentation. Take the survey.

On January 15, 2026, GitLab 18.8 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor.

This month’s Notable Contributor: Wesley Yarde

This month’s Notable Contributor is Wesley Yarde for building a foundational new feature that allows organizations to disable SSH keys for their enterprise users. Wesley’s contribution stands out for several reasons:

• Security and compliance: This feature enables organizations to enforce SSH key requirements and enhance security across their enterprise.
• Foundational work: With no existing implementation to follow, Wesley had to collaborate extensively with the GitLab team to define requirements and architecture from scratch.
• First contribution: Remarkably, this was Wesley’s first contribution to GitLab—demonstrating exceptional ability to navigate a complex codebase and tackle a challenging feature.
• Enables future development: This work establishes the foundation for similar features like instance-level SSH key disabling and service account controls. The implementation spanned multiple merge requests (!205020, !210482) with thorough review cycles. Despite the complexity, Wesley demonstrated outstanding collaboration and patience throughout the process. “It was a pleasure to collaborate with Wesley on this feature request! While both the contributor and reviewers may have felt that the review process was overwhelming, both sides showed understanding and superb collaboration to ensure the implementation is solid and complete.” — Bogdan Denkovych, who nominated Wesley for this recognition. Congratulations Wesley, and thank you for this valuable contribution to GitLab!

Primary features

GitLab Duo Agent Platform now generally available

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue GitLab Duo Agent Platform is now generally available, bringing agentic AI orchestration across your entire software development lifecycle. Unlike AI tools that speed up individual tasks in isolation, the Agent Platform helps teams coordinate AI agents across planning, building, securing, and shipping software, closing the gap between faster individual work and the collaborative, multi-stage reality of software delivery. The platform provides a central AI Catalog where teams can discover, manage, and share agents and flows across their organization. Built-in foundational agents like Planner, Security Analyst, and Data Analyst handle structured work at key decision points, while customizable flows automate multi-step agents and tasks in development workflows from issue to merge request, CI/CD migration, pipeline troubleshooting, and code reviews. With governance controls, usage visibility, and flexible deployment options including self-hosted models for offline environments, organizations can adopt AI at scale with the transparency and control they need. GitLab Premium and Ultimate users can start using the Agent Platform today on GitLab.com and GitLab Self-Managed instances with promotional GitLab Credits.

GitLab Duo Planner Agent now generally available

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue The Planner Agent is now generally available! The Planner Agent is a foundational agent built to support product managers directly in GitLab. Use the Planner Agent to create, edit, and analyze GitLab work items. Instead of manually chasing updates, prioritizing work, or summarizing planning data, the Planner Agent helps you analyze backlogs, apply frameworks like RICE or MoSCoW, and surface what truly needs your attention. It’s like having a proactive teammate who understands your planning workflow and works with you to make better, more efficient decisions. Please provide your feedback in issue 583008.

GitLab Duo Security Analyst Agent now generally available

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic The GitLab Duo Security Analyst Agent, introduced as beta in GitLab 18.5, is now generally available in GitLab 18.8. The Security Analyst Agent enables engineers to manage vulnerabilities through natural language commands in GitLab Duo Agentic Chat. Instead of manually clicking through vulnerability dashboards or writing custom scripts for bulk operations, security teams can now triage, assess, and provide guidance for vulnerabilities in Chat conversations. As a foundational agent, the Security Analyst Agent is available by default in GitLab Duo Agentic Chat, with no manual setup required.

Auto-dismiss irrelevant vulnerabilities with vulnerability management policies

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic Security teams can now automatically dismiss vulnerabilities that don’t apply to their organization using vulnerability management policies. Dismissing vulnerabilities that are not relevant to your organization reduces noise and helps developers focus on vulnerabilities that pose actual risk. You can create policies to auto-dismiss vulnerabilities based on:
• File path
• Directory
• Identifier (CVE, CWE, or OWASP) Auto-dismissed vulnerabilities appear in the merge request’s security widget with an Auto-dismissed label and are tracked in the vulnerability report activity with a dismissal reason for audit purposes.

Agentic Core

Turn the GitLab Duo Agent Platform on or off

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue You can now turn on or off the GitLab Duo Agent Platform, including GitLab Duo Chat (Agentic), agents, and flows for a top-level group or the entire instance. When this setting is turned off, these features are not available.

Group access control for GitLab Duo features

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue You can now define group access rules to control who can use GitLab Duo features, enabling flexible adoption strategies from immediate organization-wide access to phased rollouts. This feature provides granular governance control so you can scale adoption at your pace while maintaining security and compliance.

GitLab Duo Agent Platform for GitLab Duo Self-Hosted (offline licensing) now generally available

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Add-ons: Duo Enterprise
• Links: Documentation | Related epic GitLab Duo Agent Platform is now generally available for Duo Self-Hosted. This feature is available to GitLab Self-Managed customers with an offline license, and uses seat-based pricing. Self-Managed administrators can configure compatible models for use with GitLab Duo Agent Platform. Administrators using AWS Bedrock or Azure OpenAI can also configure Anthropic Claude or OpenAI GPT models.

Unified DevOps and Security

C/C++ support in Advanced SAST now generally available

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic Cross-file, cross-function scanning support for C/C++ is now generally available in GitLab Advanced SAST.

Multiple Container Scanning

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic In GitLab 18.8, we released multi-container scanning in Beta. Users are now able to pass in an array of images to be scanned as part of many Container Scanning jobs.

Centralized credential management API for group owners

• Tier: Silver, Gold
• Offering: GitLab.com
• Links: Documentation | Related epic The Credentials Inventory API is now available for Enterprise users on GitLab.com. This adds credential management capabilities previously only available on self-hosted instances, and enables organizations to better manage and secure their authentication tokens and keys. The Credentials Inventory API provides programmatic access to view credentials across your organization, including:
• Personal Access Tokens (PATs)
• Group Access Tokens (GrATs)
• Project Access Tokens (PrATs)
• SSH Keys
• GPG Keys This API complements the existing Credentials Inventory UI, allowing enterprise administrators to automate credential management tasks that previously required manual intervention. With the Credentials Inventory API, you can:
• Automate security workflows: Build automated processes to monitor, audit, and revoke credentials.
• Enforce credential policies: Identify and revoke unused or expired tokens.
• Improve security posture: Reduce the risk of credential misuse through regular auditing.
• Streamline operations: Integrate credential management into your existing security tools and workflows.

Group Owners can disable SSH keys for enterprise users

• Tier: Silver, Gold
• Offering: GitLab.com
• Links: Documentation | Related issue Group Owners can now disable SSH keys for all enterprise users in their group. When disabled, users cannot add new SSH keys and their existing keys are deactivated. This applies to all enterprise users in the group, including those with the Owner role. Thank you to Wesley Yarde for helping build this feature!

GitLab Runner 18.8

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation We’re also releasing GitLab Runner 18.8 today! GitLab Runner is the highly-scalable build agent that runs your CI/CD jobs and sends the results back to a GitLab instance. GitLab Runner works in conjunction with GitLab CI/CD, the open-source continuous integration service included with GitLab.

What’s New

• Improved error messages for job inputs interpolation errors

Bug Fixes

• WaitForServicesTimeout no longer supports -1 to disable timeout
• Custom URL breaks submodule authentication with insteadOf rules
• Custom runner short-token on Windows 2025 uses 9 characters instead 8
• PowerShell default helper image missing for Docker executor in GitLab Runner 17.8.3
• GitLab Runner with Docker Autoscaler does not reuse available cache volumes
• VirtualBox leaves dangling VM when job is cancelled The list of all changes is in the GitLab Runner CHANGELOG.

Related topics

• Bug fixes
• Performance improvements
• UI improvements
• Deprecations and removals
• Upgrade notes

Help us learn about your current experience with the documentation. Take the survey.

On December 18, 2025, GitLab 18.7 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor.

This month’s Notable Contributor: David Aniebo

We’re excited to recognize David Aniebo as our 18.7 Notable Contributor for his impactful contributions to GitLab product planning capabilities and the contributor platform. David’s work on improving work item list functionality demonstrates his technical expertise and dedication to enhancing the user experience for GitLab planning features. This contribution helps teams better organize and manage their work items, making project planning more efficient for thousands of GitLab users. Beyond code contributions, David has been a consistent supporter of the contributor platform, helping to improve the experience for community contributors. His collaborative approach and responsiveness have earned praise from multiple team members across different groups. “David has done some fantastic work helping out with some Product Planning group efforts, and we are very thankful for his contributions,” shared Nick Brandt, Engineering Manager for Product Planning. Thank you, David, for your valuable contributions to GitLab and for being such a collaborative member of our community! We look forward to your continued involvement.

Primary features

Secret validity checks improved and generally available

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic When a valid secret is leaked in one of your repositories, you must react quickly. To help you prioritize urgent threats, validity checks automatically verify whether leaked credentials can still be used. In GitLab 18.7, we’ve improved:
• Vendor integrations: Integrated with Google Cloud, AWS, and Postman, along with existing support for GitLab tokens.
• Report filtering: Filter the Vulnerability Report by validity status (active, inactive, possibly active) to quickly triage and prioritize secret findings.
• Group-level API: Turn on validity checks across all projects in a group with a single API call and streamline rollout across your organization. In this release, validity checks are generally available.

Separate model selection for Agentic Chat and agents

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Pro, Duo Enterprise
• Links: Documentation | Related issue Separate models can now be selected for Agentic Chat and for all other agents for top-level groups or instances. This provides more options for model selection for GitLab Duo Agent Platform.

Improved GitLab Duo and SDLC trends dashboard

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Core, Duo Pro, Duo Enterprise
• Links: Documentation | Related epic The GitLab Duo and SDLC trends dashboard delivers improved analytics capabilities to measure the impact of GitLab Duo on software delivery. The dashboard now provides 6-month trend analysis across GitLab Duo feature adoption, pipeline performance, and common development metrics such as deployment frequency and mean time to merge. You can now track code generation volumes and IDE or language trends for GitLab Duo Code Suggestions, and observe as your teams adopt new GitLab Duo Agent Platform flows. Enhanced user-level metrics enable teams to gain deeper insight into the key Duo features providing continuous value. A new endpoint for instance-level AI usage is now available for instance administrators to extract all Duo data from either Postgres (3-month retention) or ClickHouse. Powered by the ClickHouse integration, this dashboard delivers sub-second query performance across millions of data points. For self-managed instances, see improved recommendations and configuration guidance for ClickHouse integration.

Additional Planner Agent features available in beta

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Core, Duo Pro, Duo Enterprise
• Links: Documentation | Related issue The Planner Agent now includes create and edit features in beta! The Planner Agent is a foundational agent built to support product managers directly in GitLab. Use the Planner Agent to create, edit, and analyze GitLab work items. Instead of manually chasing updates, prioritizing work, or summarizing planning data, the Planner Agent helps you analyze backlogs, apply frameworks like RICE or MoSCoW, and surface what truly needs your attention. It’s like having a proactive teammate who understands your planning workflow and works with you to make better, more efficient decisions. Please provide your feedback in issue 576622.

Dynamic input options in CI/CD pipelines

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic You can set up your CI/CD pipelines to make use of dynamic input selection when creating new pipelines through the intuitive web interface. Now, with dynamic input options, you can configure your pipelines so that input selection options update dynamically based on previous selections. For example, when you select an input in one dropdown list, it automatically populates a list of related input options in a second dropdown list. With CI/CD inputs, you can:
• Trigger pipelines with pre-configured inputs, reducing errors and streamlining deployments.
• Enable your users to select different inputs than the defaults from dropdown menus.
• Now have cascading dropdown lists where options dynamically update based on previous selections. This dynamic capability enables you to create more intelligent, context-aware input configurations that guide you through the pipeline creation process, reducing errors and ensuring only valid combinations of inputs are selected.

SAST False Positive Detection with AI (Beta)

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Core, Duo Pro, Duo Enterprise
• Links: Documentation | Related epic Security teams often spend significant time investigating SAST findings that turn out to be false positives, diverting attention from genuine security risks. In GitLab 18.7, we’re introducing AI-powered SAST False Positive Detection to help teams focus on the vulnerabilities that matter. When a security scan runs, GitLab Duo automatically analyzes each Critical and High severity SAST vulnerability to determine the likelihood that it’s a false positive. The AI assessment appears directly in the vulnerability report, giving security engineers immediate context to make faster, more confident triage decisions. Key capabilities include:
• Automatic analysis: False positive detection runs automatically after each security scan with no manual triggering required.
• Manual trigger option: Users can manually trigger false positive detection for individual vulnerabilities on the vulnerability details page for on-demand analysis.
• Focused on high-impact findings: Scoped to Critical and High severity vulnerabilities to maximize signal-to-noise improvement.
• Contextual AI reasoning: Each assessment includes an explanation of why the finding may or may not be a true positive, based on code context and vulnerability characteristics.
• Seamless workflow integration: Results surface directly in the vulnerability report alongside existing severity, status, and remediation information. This feature is available as a free beta for Ultimate customers and must be enabled in your group or project settings. We welcome your feedback in issue 583697.

New security dashboards enabled by default

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic The new security dashboards have been updated and modernized. The dashboards were previously available on GitLab.com, and are now enabled by default on GitLab Dedicated and GitLab Self-Managed. The new features include:
• A vulnerabilities over time chart that supports:
• Filtering based on project or report type.
• Grouping by report type and severity.
• Direct links to vulnerabilities in the vulnerability report.
• A risk score module that calculates the estimated risk for a group or project based on a GitLab algorithm. Please note that using the new dashboard requires Elasticsearch.

Instance setting to control publishing of components to the CI/CD Catalog

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related issue Administrators of GitLab Self-Managed and GitLab Dedicated can now restrict which projects are allowed to publish components to the CI/CD Catalog. This new setting enables organizations to maintain a curated, trusted CI/CD Catalog by controlling what components can be published. Administrators can now specify an allowlist of projects authorized to publish components. When the allowlist is populated with projects, only those projects can publish components. This prevents unauthorized or unapproved components from cluttering the list of published components and ensures all components meet organizational standards and security requirements. This addresses a key governance challenge for enterprise customers who want to maintain control over their CI/CD component ecosystem while enabling their teams to discover and reuse approved components.

Agentic Core

Advanced search available for both merge request descriptions and comments

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related issue Advanced search now returns matching results from both merge request descriptions and comments. Previously, users had to search merge request descriptions and comments separately. This improvement provides a more streamlined and comprehensive search workflow for GitLab merge requests.

Support for AGENTS.md with GitLab Duo Chat (Agentic) in IDEs

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Core, Duo Pro, Duo Enterprise
• Links: Documentation GitLab Duo Chat now supports the AGENTS.md specification, an emerging standard for providing context and instructions to AI coding assistants. Unlike custom rules that are only available to GitLab Duo, AGENTS.md files are also available for other AI coding tools to use. This makes your build commands, testing instructions, code style guidelines, and project-specific context available to any AI tool that supports the specification. GitLab Duo Chat in your IDE automatically applies available instructions from AGENTS.md files in your repository, set at the user or workspace level. For monorepos, you can place AGENTS.md files in subdirectories to provide tailored instructions for different components.

AI agent and flow versioning

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed
• Links: Documentation | Related epic When you enable an agent or flow from the AI Catalog in your project, GitLab now pins it to a specific version. This means your AI-powered workflows stay stable and predictable even as catalog items evolve, so you can test and validate new versions before you upgrade.

AI gateway timeout setting

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Enterprise
• Links: Documentation | Related issue For GitLab Duo Self-Hosted, you can now configure a timeout value for requests to self-hosted models. This value can range from 60 to 600 seconds.

Report agents and flows to administrators

…

Help us learn about your current experience with the documentation. Take the survey.

On November 20, 2025, GitLab 18.6 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor.

This month’s Notable Contributor: Samaksh Agarwal

Every developer using the GitLab Development Kit (GDK) benefits from Samaksh’s contribution to improve the readability of gdk status. While this enhancement may appear simple on the surface, it demonstrates exceptional attention to developer experience and understanding of how small improvements can have widespread impact. The improved readability of gdk status saves time for every developer using GDK and considerably increases the accessibility of one of the core pieces of the development environment. This type of contribution shows maturity in understanding how to make meaningful improvements to the developer workflow. Reflecting on his contributions, Samaksh shares: “GitLab Development Kit (or GDK) has been my choice of active contributions for now, because I personally like to work on the side that makes experience for other contributors easy and convenient. And that’s the kind of developer I wanna be. The one that can use his skills to make others’ lives easier.” When asked about his experience contributing to GitLab, Samaksh notes: “I’d like to recommend GitLab to everyone who wants to try a fresh and quality open source experience. When I first started contributing to GitLab, I was a bit overwhelmed but everyone in the community was so supportive, helpful and welcoming that it all went away. I am absolutely in love with the community and how they do things around here. From writing excellent documentation, to maintaining peak code quality, to genuinely appreciating their contributors, GitLab community is absolutely wonderful.”

Primary features

The new GitLab UI: Designed for productivity

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related epic Introducing a smarter, more intuitive GitLab UI that puts developer productivity first. The new side-by-side design uses contextual panels to keep you in your workflow, reducing unnecessary clicks and helping teams work faster. Customize your workspace, maximize screen real estate, and enjoy a cleaner, more dynamic experience that adapts to your workflow. GitLab is committed to continuous improvement, so please share your thoughts in the feedback issue and help shape the future of GitLab.

Exact code search in limited availability

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed
• Links: Documentation | Related epic With this release, exact code search is now in limited availability. You can use exact match and regular expression modes to search for code across an entire instance, in a group, or in a project. Exact code search is built on top of the open-source search engine Zoekt. For GitLab.com, exact code search is enabled by default. For GitLab Self-Managed, an administrator must install Zoekt and enable exact code search. This feature is in active development. We welcome your feedback in issue 420920!

CI/CD Components can reference their own metadata

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related issue Previously, CI/CD components couldn’t reference their own metadata, such as version numbers or commit SHAs, within their configuration. This lack of information could cause you to use configuration with hardcoded values or complex workarounds. Writing configuration this way can lead to version mismatches when components build resources such as Docker images, because there’s no way to automatically tag those resources with the component’s compatible version. In this release, we’ve introduced the ability to access component context with the spec:component keyword. You can now build and publish versioned resources like Docker images when you release a component version, ensuring everything is in sync, eliminating manual version management, and preventing version mismatches.

Support dynamic job dependencies in needs:parallel:matrix

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related issue parallel:matrix makes it possible to easily run multiple jobs in parallel with different requirements, for example to test code for multiple platforms at the same time. But if you wanted later jobs to use needs:parallel:matrix to depend on specific parallel jobs, the configuration was complex and inflexible. Now, with the new $[[matrix.VARIABLE]] expression introduced as a Beta feature, users can create dynamic 1-1 dependencies which makes complex parallel:matrix configurations much easier to manage. This can help you create faster pipelines, with efficient artifact handling, better scalability, and cleaner configuration. This feature is particularly valuable for multi-platform builds, Terraform deployments across multiple environments, and any workflow requiring parallel processing across multiple dimensions.

GitLab Security Analyst Agent available as a foundational agent

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Core, Duo Pro, Duo Enterprise
• Links: Documentation | Related epic The GitLab Security Analyst Agent is now a foundational agent in GitLab Duo Agentic Chat. This means that users do not have to manually add the GitLab Security Analyst agent from the AI Catalog, and this agent is available by default for GitLab Self-Managed and GitLab Dedicated as well. This specialized assistant provides AI-native vulnerability management and security analysis, helping you investigate findings, triage vulnerabilities, and navigate compliance requirements without any setup. This feature is in beta, and we welcome your feedback in issue 576916.

Model selection for GitLab Duo Agentic Chat in VS Code and JetBrains IDEs

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Core, Duo Pro, Duo Enterprise
• Links: Documentation | Related epic Easily choose your preferred AI model right in GitLab Duo Chat, now available in the VS Code and JetBrains IDEs. Use the dropdown list in the GitLab Duo Chat panel to select among Claude, GPT, and other supported models. Model availability is managed by your organization admins, ensuring you have access to the right models for your workflow.

Security dashboard upgrade (beta on GitLab.com)

• Tier: Ultimate
• Offering: GitLab.com
• Links: Documentation | Related epic The new security dashboards have been updated and modernized. The initial features in the beta release include:
• A vulnerabilities over time chart that supports:
• Filtering based on project or report type.
• Grouping by report type and severity.
• Direct links to vulnerabilities in the vulnerability report.
• A risk score module that calculates the estimated risk for a group or project based on a GitLab algorithm. The new security dashboards released in 18.6 are currently available on GitLab.com only.

Agentic Core

GitLab MCP server available in beta

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Core, Duo Pro, Duo Enterprise
• Links: Documentation The GitLab MCP server is available in beta. With the GitLab MCP server, you can use AI assistants like Claude Code, Cursor, and other MCP-compatible tools to interact with your GitLab projects, issues, merge requests, and pipelines, all without building custom integrations for each tool. To get started, turn on beta and experimental features in your GitLab Duo settings. The GitLab MCP server provides key tools covering issues, merge requests, and pipelines, and we continue to refine it based on user feedback. This feature might have incomplete functionality or bugs. Try it out and share feedback in issue 561564.

Advanced search available for both issue descriptions and comments

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related issue Advanced search now returns matching results from both issue descriptions and comments. Previously, users had to search issue descriptions and comments separately. This improvement provides a more streamlined and comprehensive search workflow for GitLab issues.

Gemini 2.5 Flash model compatible with GitLab Duo Agent Platform for GitLab Duo Self-Hosted

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Add-ons: Duo Enterprise
• Links: Documentation | Related issue You can now use the Gemini 2.5 Flash model on GitLab Duo Agent Platform with GitLab Duo Self-Hosted.

Scale and Deployments

Rate limit for listing project and group members

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related issue We’ve introduced rate limiting for the /api/v4/projects/:id/members/all and /api/v4/groups/:id/members/all endpoints to improve API stability and ensure fair resource usage across all users. The GET /api/v4/projects/:id/members/all and GET /api/v4/groups/:id/members/all endpoints now have a rate limit of 200 requests per minute per user. This change helps protect GitLab instances from excessive API usage that could impact performance for all users. The limit of 200 requests per minute provides ample capacity for normal usage patterns while preventing potential abuse or unintentional resource exhaustion. If your integrations or scripts use this endpoint, ensure they handle rate limit responses appropriately (HTTP 429) and implement retry logic with backoff as needed. Most users should not be affected by this change under normal usage patterns.

Unified DevOps and Security

Increased rule coverage for secret push protection and pipeline secret detection

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation | Related issue We’ve added support for 40 new rules to GitLab’s pipeline secret detection. Some existing rules have also been updated to improve quality and reduce false positives. These changes are released in version 7.20.1 of the secrets analyzer.

Code Owners now supports inherited group memberships

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
• Links: Documentation Code ownership is critical for maintaining code quality and ensuring the right people review changes to sensitive parts of your codebase. However, managing Code Owners in organizations with complex group structures has been challenging. Previously, to reference a group in your CODEOWNERS file, that group had to be directly invited to each specific project, even if it was already a member of a parent group. Code Owners now supports groups with inherited memberships as eligible approvers:
• Groups with inherited access through parent group membership are recognized as valid code owners when Code Owners approvals are enabled.
• No need to invite groups directly to every project.
• Existing CODEOWNERS files continue to work without changes.
• Same level of control over who can approve changes to critical code paths. This change reduces administrative overhead while maintaining the security and approval requirements that Code Owners provide.

Toggle draft merge request visibility on your homepage

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government …

Help us learn about your current experience with the documentation. Take the survey.

On October 16, 2025, GitLab 18.5 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor.

This month’s Notable Contributor: Jose Gabriel Companioni Benitez

In his blog post “How GitLab Can Boost Your Professional Career”, Jose shares: “For me, the main advantage that GitLab offers, from a professional development point of view, is that it is open source.” He adds, “For GitLab, it’s important that anyone can contribute, and for that reason, they have taken the contributor onboarding process very seriously.” Jose’s journey from first-time contributor in September to Notable Contributor in October demonstrates the power of the GitLab collaborative community. Through active participation in community office hours, Discord discussions, and pairing sessions, Jose found a supportive environment that helped him quickly grow to a level 3 contributor with diverse contributions spanning documentation, code, and community support. The GitLab community offers a welcoming space where contributors support one another and grow together. Whether you’re just starting your open-source journey or looking to deepen your skills, our community is here to help you succeed. To learn more about contributing, see the GitLab Contributor Platform. Thank you, Jose, for your outstanding work! 🚀

Primary features

GitLab Duo Planner, a specialized agent and Product Manager team member (beta)

• Tier: Premium, Ultimate
• Offering: GitLab.com
• Add-ons: Duo Core, Duo Pro, Duo Enterprise
• Links: Documentation | Related issue Collaborate with GitLab Duo Planner, a GitLab Duo agent built to support product managers directly within GitLab. Instead of manually chasing updates, prioritizing work, or summarizing planning data, GitLab Duo Planner helps you analyze backlogs, apply frameworks like RICE or MoSCoW, and surface what truly needs your attention. It’s like having a proactive teammate who understands your planning workflow and works with you to make better, faster decisions. This feature is currently in beta. Please provide feedback in issue 576622.

GitLab Security Analyst Agent for Duo Agent Catalog (beta)

• Tier: Ultimate
• Offering: GitLab.com
• Add-ons: Duo Core, Duo Pro, Duo Enterprise
• Links: Documentation | Related epic Agents in GitLab Duo Agent Platform can be used to perform tasks and answer complex questions within GitLab. Users can either create custom agents to accomplish specific tasks, like creating merge requests or reviewing code, or discover GitLab agents using the AI Catalog. In GitLab 18.5, we are releasing the GitLab Security Analyst Agent as a beta feature, available in the AI Catalog. To use the GitLab Security Analyst Agent in specific projects, select and enable the agent in GitLab Duo Agentic Chat. The agent can perform the following tasks:
• List all vulnerabilities in a given project.
• Get detailed vulnerability information, including CVE data and EPSS scores.
• Confirm and dismiss vulnerabilities.
• Update vulnerability severity levels.
• Revert vulnerability status back to detected.
• Create vulnerability issues, or link vulnerabilities to existing issues. With the GitLab Security Analyst Agent, users can perform tedious security workflows through AI-powered automation and intelligent analysis, enabling engineers to focus on genuine threats while the GitLab Security Analyst Agent handles repetitive assessment and documentation. Please note that the GitLab Security Analyst Agent using GitLab Duo Chat is only available for Ultimate customers with the GitLab Duo add-on. This feature is in beta, and we welcome your feedback in issue 576916.

Maven virtual registry now available in beta

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic GitLab 18.5 introduces a comprehensive web-based interface for Maven virtual registry management. Previously, platform engineers could only configure and manage virtual registries through API calls, which makes routine maintenance tasks cumbersome and requires specialized knowledge. This web-based approach significantly reduces operational overhead for platform engineering teams. Common tasks, like clearing stale cache entries, reordering upstreams for performance optimization, and testing connectivity are now point-and-click operations. Development teams gain better visibility into their dependency configuration, enabling more informed discussions about build performance and security policies. The Maven virtual registry remains in beta for GitLab Premium and Ultimate customers. Current beta limitations include a maximum of 20 virtual registries per top-level group and 20 upstreams per virtual registry. We invite enterprise customers to participate in the Maven virtual registry beta program to help shape the final release. Please consider sharing feedback and suggestions in issue 543045.

Pick up where you left off on the new personal homepage

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic You can now access a new personal homepage that consolidates all your important GitLab activities in one place, making it easier to pick up where you left off. The homepage brings together your to-do items, assigned issues, merge requests, review requests, and recently viewed content, helping you navigate GitLab’s large surface area and stay focused on what matters the most to you.

GPT-5 now available as a model option for GitLab Duo Agentic Chat

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Pro, Duo Enterprise
• Links: Documentation | Related epic OpenAI GPT-5 is now available as a GitLab AI Vendor model when selecting a model for GitLab Duo Agent Platform. When configured by Owners of a top-level group on GitLab.com and instance Administrators on Self-Managed and Dedicated, end-users can select to use GPT-5 with GitLab Duo features. Top-level owners and administrators can continue to set organization-wide model preferences through namespace or instance settings, or allow end-user to choose from all available GitLab AI Vendor models. To get started using GPT-5, select your preferred model from the model dropdown list in GitLab Duo Chat.

Instance-wide compliance and security policy management

• Tier: Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated
• Links: Documentation Enterprise users want to manage their compliance frameworks and security policies across multiple top-level groups. This is often the case when all groups in an instance:
• Share the same compliance frameworks. For example, when all projects in a group must adhere to the ISO 27001 standard.
• Enforce similar security policies. For example, when all groups share the same pipeline execution policy. With GitLab 18.5, we introduce compliance and security policy groups to centralize the management of security policies and compliance frameworks on an instance for GitLab Self-Managed and Dedicated instances. With this release, you can now create, configure, and allocate compliance frameworks and security policies from a single top-level group and enforce them across all of the other top-level groups across your instance. With a compliance and security policy group, you have a single source of truth where you can manage and edit your compliance frameworks and security policies. Security and compliance users within the group can then apply compliance frameworks and security policies to all the projects across the instance. Compliance and security policy groups make it easier to manage and enforce your compliance and security needs across your instance. However, groups still retain the ability to create their own compliance frameworks and security policies to address specific situations or workflows that can arise in those groups. This feature is for GitLab Self-Managed and Dedicated customers. GitLab.com customers can manage frameworks and policies centrally within a single top-level group or namespace using security policy projects. Learn more about compliance and security policy groups for compliance frameworks and security policies.

DAST authentication scripts

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic You can now add scripts to your CI/CD configurations to automate DAST authentication workflows. Authentication scripts enable automating complex authentication flows, including support for time-based, one-time passwords (OTP MFA). This enhancement helps your team maintain critical security controls while conducting thorough, automated security scans. By supporting real-world authentication scenarios, scripts reduce friction and ensure accurate security assessments of production software.

Agentic Core

Additional triggers for CLI agents

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed
• Add-ons: Duo Enterprise
• Links: Documentation | Related issue You can now trigger CLI agents using additional events to give you more flexibility and control over where and when your agents take action across your projects. Along with the existing mention trigger, you can use:
• Assign: Trigger agents when a merge request or issue is assigned.
• Assign reviewer: Trigger agents when a reviewer is added to a merge request.

GitLab Duo Agent Platform for GitLab Duo Self-Hosted now in beta

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Add-ons: Duo Enterprise
• Links: Documentation | Related issue GitLab Duo Agent Platform is now in beta for GitLab Duo Self-Hosted. This feature is available to all Self-Managed GitLab Duo Enterprise customers. Self-Managed instance administrators using AWS Bedrock or Azure OpenAI can configure Anthropic Claude or OpenAI GPT models for use with GitLab Duo Agent Platform. Self-Hosted administrators can also configure compatible models to use with GitLab Duo Agent Platform.

Codestral now supported for GitLab Duo Chat (Classic)

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Add-ons: Duo Enterprise
• Links: Documentation | Related issue You can now use Mistral Codestral on GitLab Duo Self-Hosted for classic Duo Chat. This model is supported for GitLab Duo Self-Hosted customers on GitLab Self-Managed instances.

GPT OSS Models compatible with GitLab Duo Agent Platform for GitLab Duo Self-Hosted

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Add-ons: Duo Enterprise
• Links: Documentation | Related epic You can now use GPT OSS models on GitLab Duo Agent Platform with GitLab Duo Self-Hosted.

Scale and Deployments

Enhanced Admin area groups list

• Tier: Free, Premium, Ultimate
• Offering: GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic We’ve upgraded the Admin area groups list to provide a more consistent experience for GitLab administrators:
• Delayed deletion protection: Group deletions now follow the same safe deletion flow used throughout GitLab, preventing accidental data loss.
• Faster interactions: Filter, sort, and paginate groups without page reloads for a more responsive experience.
• Consistent interface: The groups list now matches the look and behavior of other group lists across GitLab. This update brings the administrator experience in line with GitLab design standards, and adds important safety features to protect your data. Future enhancements to group management will automatically appear in all group lists throughout the platform.

Updated navigation experience for groups

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic …

Help us learn about your current experience with the documentation. Take the survey.

On September 18, 2025, GitLab 18.4 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor.

This month’s Notable Contributor: Patrick Rice

Patrick Rice continues his exceptional dedication to GitLab’s open source community as contributor, maintainer, and mentor. A top 5 contributor over the past year, Patrick maintains the GitLab Terraform Provider and client-go projects, handling feature additions, releases, issue triage, and community onboarding. He embodies GitLab’s mission that everyone can contribute, having worked his way up from contributor to project maintainer. Patrick’s impact extends beyond code contributions to community building and coaching, helping new contributors get started and grow in the project. Patrick previously nominated and supported Heidi Berry who won the 17.11 Notable Contributor award. He also shared insights with the GitLab for Education team on working with students learning GitLab to help us grow the next generation of developers. “I’d love to encourage new contributors to join us in collaborating on the Terraform Provider and client-go projects,” Patrick says. “We can always use more friendly faces in our community.” “Patrick has continued relentlessly supporting the GitLab team and customers,” says Lee Tickett, Staff Fullstack Engineer at GitLab, who nominated Patrick for the award. Timo Furrer, Senior Backend Engineer at GitLab, supported the nomination. “Apart from his daily contributions to the Terraform Provider and client-go,” Timo adds, “he’s helping GitLab customers directly with their IaC journey by showcasing what is possible with the GitLab Terraform Provider.” Patrick is an Enterprise Architect at Kingland and member of the GitLab Community Core Team. This marks his second Notable Contributor award, having previously won in GitLab 15.8 in January 2023. Thanks to Patrick for his sustained contributions and dedication to supporting GitLab customers and growing our open source community!

Primary features

GitLab Duo Model Selection now generally available

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed
• Add-ons: Duo Core, Duo Pro, Duo Enterprise
• Links: Documentation | Related epic GitLab Duo Model Selection is now generally available, giving organizations greater control over which AI models power their development workflows. Owners of top-level groups on GitLab.com and administrators on Self-Managed and Dedicated can now choose a specific model from a variety of GitLab AI model vendors for use with their GitLab Duo features, accessed through the GitLab-hosted AI gateway. GitLab users that belong to multiple namespaces on GitLab.com can now also set a default namespace to ensure consistent AI model preferences across all development contexts. For more information on GitLab Duo Model Selection, read the blog.

GitLab Knowledge Graph

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic The GitLab Knowledge Graph provides rich code intelligence across your codebase. Developers can understand and navigate their projects with greater context, making it easier to plan changes, perform impact analysis, and work with GitLab Duo agents to accelerate development tasks. The GitLab Duo Agent Platform leverages the Knowledge Graph to increase the accuracy of AI agents. By mapping files and definitions across a codebase, the Knowledge Graph provides enhanced context that allows Duo agents to understand relationships across your entire local workspace—unlocking faster and more precise responses to complex questions. This release of the Knowledge Graph focuses on local code indexing, where the CLI turns your codebase into a live, embeddable graph database for RAG. You can install it with a simple one-line script, parse local repositories, and connect via MCP to query your workspace. Our vision for the Knowledge Graph project is two-fold: building a vibrant community edition that developers can run locally today, which will serve as the foundation for a future, fully integrated Knowledge Graph Service within GitLab.com and self-managed instances. This feature is in beta status. Provide feedback in issue 160.

End user model selection now available with GitLab Duo

• Tier: Premium, Ultimate
• Offering: GitLab.com
• Add-ons: Duo Core, Duo Pro, Duo Enterprise
• Links: Documentation | Related epic GitLab Duo model selection for end-users is now in public beta on GitLab.com. Users can now select their preferred model for GitLab Duo Agentic Chat directly in the GitLab UI, giving developers personalized control over their AI assistance experience. When allowed by namespace owners on GitLab.com, end-users can choose from available GitLab AI Vendor models for use with GitLab Duo Agentic Chat. Namespace owners can continue to set organization-wide model preferences through namespace settings, or allow end-user model selection. To get started, look for the model dropdown in GitLab Duo Agentic Chat to select your preferred model. Note that changing models will start a fresh conversation, and your preferences will be remembered for future sessions.

CI/CD job tokens can authenticate Git push requests

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue You can now allow CI/CD job tokens generated in your project to authenticate Git push requests to the project’s repository. Enable this with the Job token permissions settings in the UI, or alternatively with the ci_push_repository_for_job_token_allowed parameter in the project’s REST API endpoint.

GitLab Duo context exclusion

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed
• Add-ons: Duo Pro, Duo Enterprise
• Links: Documentation | Related epic GitLab Duo context exclusion allows you to control which project content is excluded as context for GitLab Duo. This is helpful to protect sensitive information such as password files and configuration files. You can exclude individual files, specific directories, specific file types, or any combination of these. This feature is currently in beta. Provide feedback on GitLab Duo context exclusion in issue 566244.

Expanded AWS region support for GitLab Dedicated

• Tier: Ultimate
• Offering: GitLab Dedicated
• Links: Documentation GitLab Dedicated now supports deployment in all AWS regions, enabling you to select from an expanded list of regions for your primary, secondary, and backup deployment location. This expansion is enabled by AWS’s rollout of io2 disks across all regions, which meet GitLab Dedicated’s standards for high availability and disaster recovery. All newly available regions can be selected when provisioning your GitLab Dedicated instance in Switchboard.

Simulate CI/CD Pipelines against different branch

• Tier: Free, Premium, Ultimate
• Offering: GitLab Dedicated
• Links: Documentation | Related issue Previously, when using the pipeline editor and validating your changes using the Validate tab, you could only run a simulation for the default branch. In this release, we’ve expanded this capability. You can now select any branch to simulate pipelines against. This improvement gives you greater flexibility in testing and validating your pipelines. You can ensure they perform as expected across different cases, including your stable branches or feature branches.

Agentic Core

Automatic Duo Code Review for groups and applications

• Tier: Premium, Ultimate
• Offering: GitLab.com
• Add-ons: Duo Enterprise
• Links: Documentation | Related issue You can now use group or application settings to enable automatic Duo Code Review for multiple projects. This can help you quickly enable Duo Code Review for all projects in a group, rather than individually enabling specific projects. This feature is currently available in GitLab.com, and we plan to make it available for GitLab Self-Managed in a future release. Provide feedback in issue 517386.

Additional supported models for GitLab Duo Self-Hosted

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Add-ons: Duo Enteprise
• Links: Documentation | Related epic GitLab Self-Managed customers with GitLab Duo Enterprise can now use additional supported models with GitLab Duo. OpenAI GPT-5 is now supported on Azure OpenAI. Open source OpenAI GPT OSS 20B and 120B aer also now supported on vLLM and Azure OpenAI. To leave feedback on using these models with GitLab Duo Self-Hosted, see issue 523918.

Duo Code Review on GitLab Duo Self-Hosted is generally available

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Add-ons: Duo Enterprise
• Links: Documentation | Related issue GitLab Duo Code Review on GitLab Duo Self-Hosted is now generally available. Use Code Review on GitLab Duo Self-Hosted to accelerate your development process without compromising on data sovereignty. When Code Review reviews your merge requests, it identifies potential bugs and suggests improvements for you to apply directly. Use Code Review to iterate on and improve your changes before you ask a human to review. This feature includes support for Mistral, Meta Llama, Anthropic Claude, and OpenAI GPT model families. Provide feedback on Code Review in issue 517386.

Unified DevOps and Security

Pipeline secret detection now excludes certain files and directories by default

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue Pipeline secret detection now automatically excludes certain file types and directories if they have a low likelihood of containing secrets, improving scan performance. These changes are released in analyzer version 7.11.0.

Secret detection analyzer Git fetching improvements

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic Version 7.12.0 of the secret detection analyzer adds significant improvements to the way Git commits are fetched. The analyzer now parses --depth and --since options passed from SECRET_DETECTION_LOG_OPTIONS, so you can further specify how many commits you want to scan. The analyzer also selects appropriate fetch strategies based on context, which prevents a known issue where potentially millions of commits were unnecessarily fetched, even with shallow depth configurations. This enhancement reduces job timeouts, decreases resource consumption, and provides more predictable scan performance. Experience faster secret detection scans, especially in large repositories, with clearer logging that matches the actual fetching behavior.

Significantly faster Advanced SAST scanning

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic Every minute counts when you’re enabling security scans in your merge requests and pipelines. We routinely ship performance improvements for Advanced SAST, targeting both the engine and its detection rules. In this release, we’re highlighting a specific improvement that cuts scan runtime by as much as 78% in our benchmark and real-world tests. We’ve added caching in a performance-sensitive part of the scanning process, leading to significantly faster scans in large repositories. This improvement is automatically enabled in Advanced SAST analyzer version 2.9.6 and later. You can see which analyzer version you’re using by checking scan job logs.

Operational Container Scanning severity threshold configuration

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue …

Help us learn about your current experience with the documentation. Take the survey.

On August 21, 2025, GitLab 18.3 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor.

This month’s Notable Contributor: Ahmed Kashkoush

For 18.3, we’re excited to recognize Ahmed Kashkoush as our Notable Contributor! Ahmed has been a standout contributor to the GitLab Web IDE through his Google Summer of Code participation this summer. He has consistently delivered essential Git operations, directly addressing long-standing community requests. His five substantial merge requests include commit and force push capabilities, update confirmation message, commit amend functionality, branch creation operations, and branch deletion features. Beyond implementing new features, Ahmed resolved a 5+ year old feature request for amending existing commits from the Web IDE, a feature with 24 thumbs up from the community. His comprehensive branch management implementation brings the Web IDE closer to feature parity with local development environments, eliminating the need for users to switch between interfaces for basic Git operations. Ahmed’s work directly supports GitLab’s mission that “everyone can contribute” by making the Web IDE more accessible to developers. Ahmed was nominated by Enrique Alcántara, Staff Frontend Engineer at GitLab, who served as his mentor throughout the Google Summer of Code program. “Ahmed shows dedication to solving real user pain points,” says Enrique. “His work demonstrates the impact a focused contributor can have on improving core GitLab functionality.” Ahmed’s contributions showcase the power of mentorship and community collaboration in open source development and make GitLab more accessible to developers regardless of their local setup. Thank you, Ahmed, for your exceptional contributions to GitLab’s Web IDE!

Primary features

Duo Agent Platform in Visual Studio (Beta)

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed
• Links: Documentation | Related epic We are excited to announce the public beta release of the Duo Agent Platform for Visual Studio! With this release, Visual Studio users can now access Duo Agent Platform’s advanced AI-powered capabilities directly within their IDE. The Duo Agent Platform brings two powerful features to your workflow:
• Agentic chat: Quickly accomplish conversational tasks such as creating and editing files, searching your codebase with pattern matching and grep, and getting instant answers about your code—all without leaving Visual Studio.
• Agent flows: Tackle larger, more complex tasks with comprehensive planning and implementation support. Agent flows help you turn high-level ideas into architecture and code, leveraging GitLab resources like issues, merge requests, commits, CI/CD pipelines, and security vulnerabilities. Both features offer intelligent search across documentation, code patterns, and project information, empowering you to move seamlessly from quick edits to in-depth project analysis. Try the Duo Agent Platform beta in Visual Studio today and experience a new level of productivity and AI assistance in your development workflow.

Embedded views (powered by GLQL)

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic This release introduces embedded views, powered by GLQL, to general availability. Create and embed dynamic, queryable views of GitLab data directly where your work lives: in wiki pages, epic descriptions, issue comments, and merge requests. Embedded views provide a stable foundation for teams to track work progress without navigating between multiple locations. Query issues, merge requests, epics, and other work items using familiar syntax, then display the results as tables or lists with customizable fields and filtering. Embedded views transform static documentation into living dashboards that stay current with your project data, helping teams maintain context and improve collaboration across their workflows. We welcome your feedback as we continue to enhance embedded views. Please share your thoughts and suggestions in our feedback issue.

Migration by direct transfer

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic Migration by direct transfer is now generally available. To migrate GitLab groups and projects between GitLab instances by direct transfer, you can use the GitLab UI or the REST API. Compared to migration by uploading an export file, direct transfer:
• Works more reliably with large projects.
• Supports migrations with a larger version gap between the source and destination instances.
• Offers better insights into the migration process and results. On GitLab.com, migration by direct transfer is enabled by default. On GitLab Self-Managed and GitLab Dedicated, an administrator must enable the feature.

Fine-grained permissions for CI/CD job tokens

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic Pipeline security just got more flexible. Job tokens are ephemeral credentials that provide access to resources in pipelines. Until now, these tokens inherited full permissions from the user, often resulting in unnecessarily broad access capabilities. With our new fine-grained permissions for job tokens feature, you can now precisely control which specific resources a job token can access within your projects. This allows you to implement the principle of least privilege in your CI/CD workflows, granting only the minimal access necessary for jobs to complete their tasks when accessing your projects with the CI/CD job token. We’re actively working to add additional fine-grained permissions to reduce reliance on long-lived tokens in pipelines.

Code Review available on GitLab Duo Self-Hosted (Beta)

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Add-ons: Duo Enterprise
• Links: Documentation | Related issue You can now use GitLab Duo Code Review on GitLab Duo Self-Hosted. This feature is in beta on GitLab Duo Self-Hosted, with support for Mistral, Meta Llama, Anthropic Claude, and OpenAI GPT model families. Use Code Review on GitLab Duo Self-Hosted to accelerate your development process without compromising on data sovereignty. When Code Review reviews your merge requests, it identifies potential bugs and suggests improvements for you to apply directly. Use Code Review to iterate on and improve your changes before you ask a human to review. Provide feedback on Code Review in issue 517386.

Customize instructions for GitLab Duo Code Review

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Enterprise
• Links: Documentation | Related issue Enforce consistent code review standards across your projects with custom instructions for GitLab Duo Code Review. Define specific review criteria for different file types using glob patterns, ensuring language-specific conventions are applied where they matter most. With custom instructions, you can:
• Describe your team’s code review standards
• Use glob patterns to define file-specific instructions
• Observe clearly labeled feedback that references your custom instructions Simply create a .GitLab/duo/mr-review-instructions.YAML file in your repository with your custom instructions. GitLab Duo will automatically incorporate these instructions into its reviews, citing the specific instruction group when providing feedback. Help us improve this feature by sharing your thoughts and suggestions in our feedback issue.

Bring your own models to GitLab Duo Self-Hosted (Beta)

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Add-ons: Duo Enterprise
• Links: Documentation | Related issue GitLab Duo Self-Hosted now enables you to bring your own model to use with GitLab Duo features. This feature is in beta, and available to all GitLab Self-Managed customers with GitLab Duo Enterprise. Instance administrators can configure any compatible model for use with a supported GitLab Duo feature. This feature makes GitLab Duo Self-Hosted more flexible, but GitLab cannot guarantee that all GitLab Duo features will work with every compatible model. Instance administrators are responsible for validating the compatibility and performance of their chosen model. GitLab does not provide technical support for issues specific to your chosen model or platform.

Hybrid model selection on GitLab Duo Self-Hosted (Beta)

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Add-ons: Duo Enterprise
• Links: Documentation | Related epic You can now use a mix of GitLab AI vendor models and privately configured self-hosted models on GitLab Duo Self-Hosted. This feature is in beta and available on GitLab Self-Managed to all GitLab Duo Enterprise customers. With hybrid models on GitLab Duo Self-Hosted, GitLab Self-Managed instance administrators can now choose between a self-hosted model and self-hosted AI gateway, or a GitLab AI vendor model and the GitLab-hosted AI gateway, on a feature-by-feature basis. This enables administrators to balance their security and scalability requirements. To provide feedback on hybrid model selection, see issue 561048.

Surfacing violations of compliance framework controls (Beta)

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation Previously, the compliance violations report provided a high-level view of merge request activity for all projects in a group. The available compliance violations related to separation of duty concerns, such as:
• Detecting when an author of a merge request approved their own merge request.
• When a merge request was merged with fewer than two approvals. However, user feedback revealed that users found violation classifications confusing and difficult to understand, due to not aligning well with actual compliance use cases. GitLab 18.3 significantly enhances the violations report by expanding beyond separation of duty to include violations of compliance controls and requirements in compliance frameworks. Each custom compliance framework control has an associated audit event that provides detailed context about violations: who committed the violation, when it occurred, and how to fix it. This includes the user’s name and IP address, plus actionable remediation suggestions. These improvements give compliance managers more powerful and relevant context to ensure their organization adheres to specific compliance frameworks, while providing reassurance that non-compliance can be effectively identified, rectified, and prevented.

New Web IDE source control operations

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation We’re excited to announce additional source control functionalities in the Web IDE. You can manage your Git workflow more efficiently without leaving your browser. In the Source Control panel, you can now:
• Create and delete branches.
• Create a branch from any existing branch as your base.
• Amend your last commit for quick fixes.
• Force push changes directly from the interface. These enhancements bring Git operations right to your fingertips. For information about the functionalities available to you, see Use source control.

AWS Secrets Manager support for GitLab CI/CD

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic …

Help us learn about your current experience with the documentation. Take the survey.

On July 17, 2025, GitLab 18.2 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor.

This month’s Notable Contributor: Markus Siebert

Markus Siebert, a Platform Engineer at DB Systel GmbH, is leading the community effort to bring native AWS Secrets Manager support to GitLab CI/CD, addressing a critical enterprise need for secure secret management in pipelines. With an impressive 172 documented activities in just 6 weeks, Markus has been working tirelessly on implementing both AWS Secrets Manager and AWS Systems Manager Parameter Store support through multiple merge requests including Add functionality to retrieve secrest from AWS Secrets Manager, Add GitLab CI config entry for AWS SSM ParameterStore, and Documentation for AWS Secrets Manager. “Markus’s work directly enables GitLab users in AWS environments to securely manage their CI/CD secrets without relying on third-party tools or custom scripts. This is especially valuable for enterprise users who have standardized on AWS services,” says Aditya Tiwari, Senior Backend Engineer, Secure at GitLab, who nominated Markus. Markus’s dedication to seeing this feature through - from initial implementation to documentation - while actively maintaining and improving merge requests based on feedback, exemplifies the best of community contribution and demonstrates the power of community-driven development in making GitLab better for AWS users. This contribution was delivered through the GitLab Co-Create Program. Thanks to Markus for your valuable contributions to GitLab!

Primary features

Duo Agent Platform in the IDE (Beta)

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed
• Add-ons: Duo Core, Duo Pro, Duo Enterprise
• Links: Documentation | Related issue The Duo Agent Platform brings agentic chat and agent flows directly into VS Code and JetBrains IDEs, enabling natural conversation-based interaction with your codebase and GitLab projects. Agentic chat is designed for quick, conversational tasks like creating and editing files, searching across your codebase with pattern matching and grep, and getting immediate answers about your code. Agent flows handle larger implementations and comprehensive planning, taking high-level ideas from concept to architecture while accessing GitLab resources including issues, merge requests, commits, CI/CD pipelines, and security vulnerabilities. Both provide intelligent search capabilities for documentation, code patterns, and project discovery to help you accomplish everything from quick edits to complex project analysis. The platform also supports Model Context Protocol (MCP) for connecting to external data sources and tools, allowing AI features to leverage context beyond GitLab. Learn more in our blog GitLab Duo Agent Platform Public Beta: Next-gen AI orchestration and more. To get started, see the Duo Agent Platform documentation, VS Code setup guide, and JetBrains setup guide.

Custom workflow statuses for issues and tasks

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic Move beyond the basic open/closed system with configurable status that lets you track work items through your team’s actual workflow stages. Instead of relying on labels, you can now define custom statuses that accurately reflect your process. With configurable statuses, you can:
• Define custom workflows that match your team’s actual process.
• Replace workflow labels with proper statuses that are easier to find, update, and report on.
• Clarify completion outcomes beyond closing an issue using “Done” or “Canceled”.
• Filter and report accurately on work item status for better project insights.
• Use status in issue boards with automatic updates when issues move between columns.
• Bulk update status across multiple work items for efficient workflow management.
• Track dependencies with status visibility for linked work items. Custom workflow statuses also support quick actions in comments and automatically syncs with GitLab’s open/closed system. Help us improve this feature by sharing your thoughts and suggestions in our feedback issue.

New merge request homepage

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic Managing code reviews across multiple projects can be overwhelming when you’re juggling dozens of merge requests as both an author and reviewer. The new merge request homepage transforms how you navigate your review workload by intelligently prioritizing what needs your attention right now, with two powerful viewing modes:
• Workflow view organizes merge requests by their review state, grouping work by its stage in the code review workflow.
• Role view groups your merge requests by whether you’re the author or reviewer, giving you a clear separation of responsibilities. The Active tab shows merge requests requiring attention, Merged displays recently completed work, and Search provides comprehensive filtering capabilities. The new homepage also expands your visibility by combining both authored and assigned merge requests, ensuring you never miss work that’s been delegated to you.

Improve security with immutable container tags (Beta)

• Tier: Ultimate
• Offering: GitLab Dedicated
• Links: Documentation | Related epic Container registries are critical infrastructure for modern DevSecOps teams. However, even with protected container tags, organizations still face a challenge: After a tag is created, users with sufficient permissions can alter it. This creates risks for teams that rely on specific tagged versions of container images for production stability. Any modification—even by authorized users—can introduce unintended changes or compromise deployment integrity. With immutable container tags, you can protect container images from unintended changes. After a tag is created that matches an immutable rule, no one can modify the container image. You can now:
• Create up to 5 total protection rules per project (combining both protected and immutable rules) using RE2 regex patterns.
• Protect critical tags like latest, semantic versions (for example, v1.0.0), or release candidates from any modification.
• Ensure immutable tags are automatically excluded from cleanup policies. Immutable container tags require the next-generation container registry, which is enabled by default on GitLab.com. For GitLab Self-Managed instances, you must enable the metadata database to use immutable container tags.

Group and project controls for Premium and Ultimate with GitLab Duo

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue GitLab Premium and Ultimate users can now change the availability of Code Suggestions and GitLab Duo Chat in the IDE for groups and projects. Previously, you could change the availability for the instance or top-level group only.

New group overview compliance dashboard

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic The compliance center is the central location for compliance teams to manage their compliance status reporting, violations reporting, and compliance frameworks for their group. The new group overview compliance dashboard gives compliance managers an aggregated view on compliance information across all of the projects in a group. This first iteration displays the following information:
• % of projects covered by a certain compliance framework.
• % of failed requirements for all projects in a group.
• % of failed controls for all projects in a group.
• The specific frameworks that require ‘attention’. With this new group overview, compliance managers now have a single unified view that provides them with a clear high-level picture, of their compliance posture.

Map workspace Kubernetes agents for the instance

• Tier: Premium, Ultimate
• Offering: GitLab Dedicated
• Links: Documentation | Related epic GitLab administrators can now map enabled workspace Kubernetes agents for the instance. Users can then create workspaces from any group or project in that instance. This significantly increases workspace scalability by allowing organizations to provision workspace Kubernetes agents once, and make those agents accessible to all current and future projects across the entire instance.

Download a PDF export of security reports

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic To communicate the state and progress of your vulnerability management efforts to other stakeholders, you can now export the security dashboard for each project or group as a PDF document.

Centralized Security Policy Management (Beta)

• Tier: Ultimate
• Offering: GitLab Self-Managed
• Links: Documentation | Related epic In large organizations where compliance is critical, teams often struggle with fragmented policies scattered across multiple projects and groups. Without centralized visibility, ensuring consistent enforcement becomes a time-consuming challenge while increasing compliance risk. Centralized security policy management introduces a unified approach to creating, managing, and enforcing security policies across your entire GitLab organization through a single designated compliance and security policy (CSP) group. This allows security teams to:
• Define policies once and apply everywhere: Create instance-wide security policies once through the CSP and automatically enforce the policies across all groups and projects.
• Configure business unit policies: Top-level groups can configure their own distinct set of policies while inheriting organization policies from the CSP group.
• Ensure adherence to principle of least privilege: Establish a central policy management layer enforced for the instance. This beta release establishes the foundational framework for centralized policy management, with support for all existing security policy types, configurable for groups, projects, or instance.

Agentic Core

Mistral Small now available for GitLab Duo Self-Hosted

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Add-ons: Duo Enterprise
• Links: Documentation | Related epic You can now use Mistral Small on GitLab Duo Self-Hosted. This model is available on GitLab Self-Managed instances, and is the first fully compatible open source model for GitLab Duo Chat and Code Suggestions on GitLab Duo Self-Hosted.

Scale and Deployments

Administrators can reassign contributions without user confirmation

• Tier: Free, Premium, Ultimate
• Offering: GitLab Dedicated
• Links: Documentation | Related issue Administrators can now reassign contributions from placeholder users to active users without user confirmation. This feature addresses a key challenge for larger organizations where the process stalled when users did not check their emails to approve reassignments. On GitLab instances where user impersonation is enabled, administrators can maintain data integrity while streamlining user management workflows. Users still receive notification emails after the reassignment is complete, ensuring transparency throughout the process.

Reassign from placeholder users to inactive users

• Tier: Free, Premium, Ultimate
• Offering: GitLab Dedicated
• Links: Documentation | Related issue Previously, administrators could reassign contributions and memberships from placeholder users to active users only. …

Help us learn about your current experience with the documentation. Take the survey.

On June 19, 2025, GitLab 18.1 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor.

This month’s Notable Contributor: Chaitanya Sonwane

Chaitanya Sonwane drives GitLab’s security capabilities through consistent authentication improvements. With 13 merged contributions in 2025, his work enhanced credential inventory filtering, service account management, and work items usability. He previously delivered a key feature in GitLab 17.11 with token statistics for service accounts, which provides “at a glance” information that makes it easier to manage service accounts. Chaitanya is now improving work item list sort settings to be context specific, further enhancing the user experience in GitLab’s Product Planning. Chaitanya’s work directly strengthens security for GitLab organizations and provides better visibility into service account usage across projects. Teams can now track and rotate credentials more effectively. This reduces the risk of orphaned or forgotten credentials that create security vulnerabilities. “Chaitanya’s contributions to the credential inventory and service accounts are both very valuable contributions in the security space,” says Eduardo Sanz-Garcia, Senior Frontend Engineer for the Authentication group, Software Supply Chain Security stage. Eduardo supported the nomination from GitLab’s Authentication team. “Chaitanya was instrumental in the implementation of the token statistics concept,” Eduardo adds. “His credential inventory work delivered a highly requested feature to enhance the tractability and monitoring of credentials. This was a great contribution!” Chaitanya is a Software Engineer at TATA AIG. He proactively tackles security issues and follows up consistently on improvements to his own contributions. Thanks to Chaitanya for contributing to GitLab’s security foundation and the rest of the product!

Primary features

Maven virtual registry now available in beta

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Links: Documentation | Related epic The Maven virtual registry simplifies Maven dependency management in GitLab. Without the Maven virtual registry, you must configure each project to access dependencies from Maven Central, private repositories, or the GitLab package registry. This approach slows builds with sequential repository queries and complicates security auditing and compliance reporting. The Maven virtual registry addresses these issues by aggregating multiple upstream repositories behind a single endpoint. Platform engineers can configure Maven Central, private registries, and GitLab package registries through one URL. Intelligent caching improves build performance and integrates with GitLab’s authentication systems. Organizations benefit from reduced configuration overhead, faster builds, and centralized access control for improved security and compliance. The Maven virtual registry is currently available in beta for GitLab Premium and Ultimate customers on both GitLab.com and GitLab Self-Managed. The GA release will include additional capabilities, such as a web-based user interface for registry configuration, shareable upstream functionality, lifecycle policies for cache management, and enhanced analytics. Current beta limitations include a maximum of 20 virtual registries per top-level groups and 20 upstreams per virtual registry, with API-only configuration available during the beta period. We invite enterprise customers to participate in the Maven virtual registry beta program to help shape the final release. Beta participants will receive early access to the capabilities, direct engagement with GitLab product teams, and priority support during evaluation. To join the beta program, express interest and provide your use case details in issue 498139, and share feedback and suggestions in issue 543045.

Duo Code Review is now generally available

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Enterprise
• Links: Documentation Duo Code Review is now generally available and ready for production use. This AI-powered code review assistant transforms the traditional code review process by providing intelligent, automated feedback on your merge requests. It helps identify potential bugs, security vulnerabilities, and code quality issues before human reviewers get involved, making the entire review process more efficient and thorough. It includes:
• Automated initial review: Duo Code Review analyzes your code changes and provides comprehensive feedback on potential issues, improvements, and best practices.
• Interactive refinement: Mention @GitLabDuo in merge request comments to get targeted feedback on specific changes or questions.
• Actionable suggestions: Many suggestions can be applied directly from your browser, streamlining the improvement process.
• Context-aware analysis: Leverages understanding of the changed files to provide relevant, project-specific recommendations. To request a code review:
• In your merge request, add @GitLabDuo as a reviewer using the /assign_reviewer @GitLabDuo quick action, or assign GitLab Duo directly as a reviewer.
• Mention @GitLabDuo in comments to ask specific questions or request focused feedback on any discussion thread.
• Enable automatic reviews in your project settings to have GitLab Duo automatically review all new merge requests. Duo Code Review helps teams maintain higher code quality standards while reducing the time spent on manual review cycles. By catching issues early and providing educational feedback, it serves as both a quality gate and a learning tool for development teams. **Watch an overview of Duo Code Review in action from our beta release. Share your experience and feedback in issue 517386 to help us continue improving this feature.

Compromised password detection for native GitLab credentials

• Tier: Free, Silver, Gold
• Offering: GitLab.com
• Links: Documentation | Related issue GitLab.com now performs a secure check of your account credentials when you sign in to GitLab.com. If your password is part of a known leak, GitLab displays a banner and sends you an email notification. These notifications include instructions for how to update your credentials. For maximum security, GitLab recommends using a unique, strong password for GitLab, enabling two-factor authentication, and regularly reviewing your account activity. Note: This feature is only available for native GitLab usernames and passwords. SSO credentials are not checked.

Achieve SLSA Level 1 compliance with CI/CD components

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic You can now achieve SLSA Level 1 compliance using GitLab’s new CI/CD components for signing and verifying SLSA-compliant artifact provenance metadata generated by GitLab Runner. The components wrap Sigstore Cosign functionality in reusable modules that can be easily integrated into CI/CD workflows.

Scale and Deployments

Multiple matches per file in code search

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic Exact code search (in beta) now consolidates multiple search results from the same file into a single view. This improvement:
• Preserves context between adjacent matches instead of displaying isolated lines.
• Reduces visual clutter by eliminating duplicate content when matches are close together.
• Enhances navigation by clearly showing the number of matches per file.
• Improves readability by displaying code as you would see it in your editor. With this change, finding and understanding code patterns across your repositories is now more efficient.

New accessLevels argument for projectMembers in GraphQL API

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue We’re excited to announce the addition of the accessLevels argument to the projectMembers field in our GraphQL API. Use this argument to filter project members by access level directly from an API call. Previously, you had to fetch an entire list of project members and apply filters locally, which added significant computational overhead. Now, analyzing project permissions and generating ownership graphs is faster and more resource-efficient. This enhancement is particularly valuable to organizations managing large-scale deployments with complex permission structures.

Unified DevOps and Security

DAST detection parity with secret detection default rules

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue The DAST analyzer now automatically ingests the same default secret detection rules that are used by GitLab’s Secret Detection analyzer. This improvement ensures consistency in the types of secrets detected by both.

Define a Name for external custom controls

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue Previously, you couldn’t define a name for an external custom control when creating a custom compliance framework, which made it difficult to identify external controls when listed alongside GitLab controls. We’ve now added a Name field as part of the workflow when defining an external custom control, so you can create multiple external custom controls and clearly define each one with its own unique name.

Pagination for requirements in compliance frameworks UI

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue When creating a compliance framework, you can specify a maximum of 50 requirements. However, it becomes very difficult to navigate a compliance framework with this many requirements because they consume a lot of space in the user interface. In this release, we have introduced pagination for requirements to make it easier for users to navigate, find, and select requirements when there is a large number of them attached to a compliance framework.

UI performance and filtering improvements for compliance center

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation We have continued to improve the UI performance and filtering options provided by the compliance center. In this release, we have:
• Improved the UI speed and performance of the Edit Framework page, especially where there are many requirements and projects on the page.
• Introduced new filtering options so that you can group by requirement, project, or framework in the Compliance status report tab in the compliance center. By delivering these improvements, we continue to ensure that the compliance center and associated functions continue to perform at scale for customers who regularly use the compliance center.

Control status pop-up in the compliance status report

• Tier: Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue Controls in the compliance status report have three different statuses:
• Pass
• Fail
• Pending No matter the number of controls that are attached to the requirement, if at least one control was ‘pending’, the entire requirement row was shown as ‘pending’ as well. This deviated from the established UX pattern for visualizing failed controls, where the requirement would show the number of controls associated with the requirement, even when there was at least one control that fails. …

Help us learn about your current experience with the documentation. Take the survey.

On May 15, 2025, GitLab 18.0 was released with the following features. In addition, we want to thank all of our contributors, including this month’s notable contributor.

This month’s Notable Contributor: Michael Hofer

Michael Hofer champions GitLab’s open source mission as both a top contributor and community leader. With over 50 contributions this year, his work strengthened GitLab’s Geo features and Secrets Manager, based on OpenBao. He topped the April Hackathon while supporting fellow contributors and leading community projects. “I truly appreciate that everyone can contribute to GitLab!” says Michael. “The team is great to work with, it’s a lot of fun, and everyone is super helpful, especially when we team up across open source initiatives like OpenBao and SLSA.” Michael is the CTO at Adfinis, an international IT service provider specializing in planning, building, and running mission critical open source workloads. He is passionate about fostering collaboration and promoting open source solutions across organizations. Recently, Adfinis participated in GitLab’s Co-Create program, which pairs organizations with GitLab’s product and engineering teams to build GitLab together. “We highly recommend Co-Create to all organizations,” Michael says. “It led to a number of cool contributions, including rootless Podman builds, Glimmer syntax highlighting, and other improvements.” “The Geo Team really appreciates and enjoys working with Michael,” says Lucie Zhao, Engineering Manager at GitLab, who nominated Michael for the award. “With his excellent contributions over the last few milestones, he has become the most well-known community contributor within our team.” GitLab team members Lee Tickett, Chloe Fons, and Alex Scheel supported the nomination. Alex adds, “Michael’s leadership in OpenBao has enabled us to effectively collaborate in bringing forward a secrets management solution for our customers, with the transparency that aligns with our GitLab values.” Thanks to Michael and the Adfinis team for co-creating GitLab!

Primary features

GitLab Premium and Ultimate with Duo

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Pro, Duo Enterprise
• Links: Documentation | Related issue We’re excited to announce GitLab Premium with Duo and GitLab Ultimate with Duo. GitLab Premium and Ultimate now include AI-native features. GitLab’s AI-native features include Code Suggestions and Chat within the IDE. Development teams can use these features to:
• Analyze, understand, and explain code
• Write secure code faster
• Quickly generate tests to maintain code quality
• Easily refactor code to improve performance or use specific libraries

Repository X-Ray now available on GitLab Duo Self-Hosted

• Tier: Premium, Ultimate
• Offering: GitLab Self-Managed
• Add-ons: Duo Enterprise
• Links: Documentation | Related epic You can now use Repository X-Ray with Code Suggestions on GitLab Duo Self-Hosted. This feature is in beta for GitLab Duo Self-Hosted, and is generally available on GitLab Self-Managed instances.

Automatic reviews with Duo Code Review

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Enterprise
• Links: Documentation Duo Code Review provides valuable insights during the review process, but currently requires you to manually request reviews on each merge request. You can now configure GitLab Duo Code Review to run automatically on merge requests by updating your project’s merge request settings. When enabled, Duo Code Review automatically reviews merge requests unless:
• The merge request is marked as draft.
• The merge request contains no changes. Automatic reviews ensure that all code in your project receives a review, consistently improving code quality across your codebase.

Code Suggestions prompt caching

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Pro, Duo Enterprise
• Links: Documentation | Related epic Code Suggestions now includes prompt caching. Prompt caching significantly improves code completion latency by avoiding the re-processing of cached prompt and input data. The cached data is never logged to any persistent storage, and you can optionally disable prompt caching in the GitLab Duo settings.

Improved Duo Code Review context

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Add-ons: Duo Enterprise
• Links: Documentation Duo Code Review now provides more comprehensive context for improved analysis. The key improvements are:
• Includes a merge request’s title and description to better understand the purpose of proposed changes.
• Examines all diffs simultaneously to recognize cross-file relationships and reduce false positives.
• Provides the full content of changed files to understand how modifications fit within existing code patterns. These enhancements reduce inaccurate suggestions and deliver more relevant and higher quality code reviews.

Scale and Deployments

List only Enterprise users for contributions reassignment on GitLab.com

• Tier: Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed
• Links: Documentation | Related issue In this release we’ve improved the placeholder users mapping experience by narrowing down the user selection dropdown to only Enterprise users associated with the top-level group. Previously, when reassigning users’ contributions after an import to GitLab.com, you would see in the dropdown list all active users on the platform, making it difficult to identify the correct user, especially when SCIM provisioning had modified usernames. Now, if your top-level group uses the Enterprise users feature, the dropdown list will display only users claimed by your organization, significantly reducing the potential for errors during user reassignment. The same scoping is also applied to CSV-based reassignment, preventing accidental assignment to users outside your organization.

Support for multiple workspaces in the GitLab for Slack app

• Tier: Free, Premium, Ultimate
• Offering: GitLab Dedicated
• Links: Documentation | Related issue The GitLab for Slack app now supports multiple workspaces for GitLab Self-Managed and GitLab Dedicated customers. Enabling multiple workspaces allows organizations with federated Slack environments to maintain seamless GitLab integrations across all their workspaces. To enable support for multiple workspaces, configure the GitLab for Slack app as an unlisted distributed app.

Delete groups and placeholder users

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue In GitLab 18.0, when you delete a top-level group, placeholder users associated with the group are deleted as well. If placeholder users are associated with other projects, they are only removed from the top-level group. This way, unnecessary placeholder users are removed without disrupting the history or attributions of other projects.

Internal releases available for GitLab Dedicated

• Tier: Ultimate
• Offering: GitLab Dedicated
• Links: Documentation | Related epic GitLab Dedicated customers with strict security requirements and compliance obligations require the highest level of protection for their development environments. Today, we’re introducing Internal Releases, a new private release that allows us to remediate GitLab Dedicated instances for critical vulnerabilities before public disclosure, ensuring GitLab Dedicated customers are never exposed to them. This new capability delivers immediate protection for critical vulnerabilities found in GitLab parallel to response for GitLab.com. This new process does not require customer action.

GitLab chart 9.0 released with breaking changes

• Tier: Free, Premium, Ultimate
• Offering: GitLab Self-Managed
• Links: Documentation | Related issue
• Breaking change: Support for PostgreSQL 14 and 15 has been removed. Make sure you are running PostgreSQL 16 before upgrading.
• Breaking change: The bundled Prometheus chart was updated from 15.3 to 27.11. Along with the Prometheus chart upgrade, the Prometheus version was updated from 2.38 to 3.0. Manual steps are required to perform the upgrade. If you have Alertmanager, Node Exporter, or Pushgateway enabled, you must also update your Helm values. For more information, see the migration guide.
• Breaking change: The default NGINX controller image was updated from version 1.3.1 to 1.11.2. If you’re using the GitLab NGINX chart, and you have set your own NGINX RBAC rules, new RBAC rules must exist. For more information, see the upgrade guide for more information.

Event data collection

• Tier: Free, Premium, Ultimate
• Offering: GitLab Dedicated
• Links: Documentation | Related issue In GitLab 18.0, we are enabling event-level product usage data collection from GitLab Self-Managed and GitLab Dedicated instances. Unlike aggregated data, event-level data provides GitLab with deeper insights into usage, allowing us to improve user experience on the platform and increase feature adoption. For detailed instructions on how to adjust data sharing settings, please refer to our documentation.

Deletion protection available for all users

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related epic | Related issue Project and group delayed deletion is now available for all GitLab users, including those on our Free tier. This essential safety feature adds a grace period (7 days on GitLab.com) before deleted groups and projects are permanently removed. This feature allows recovery from accidental deletions without complex recovery operations. By making data safety a core feature, GitLab can help better protect your work against data loss events.

Delayed project deletion for user namespaces

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation | Related issue Delayed project deletion is now available for projects in user namespaces (personal projects). Previously, this safeguard against accidental data loss was only available for group namespaces. When you delete a project in your user namespace, it will now enter a “pending deletion” state for the duration configured in your instance settings (7 days on GitLab.com), rather than being immediately deleted. This creates a recovery window during which you can restore the project if needed. We hope this enhancement provides greater peace of mind when managing your personal projects in GitLab.

New active parameter for Groups and Projects REST APIs

• Tier: Free, Premium, Ultimate
• Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
• Links: Documentation We’ve added a new active parameter to our Groups and Projects REST APIs that simplifies filtering groups based on their status. When set to true, only non-archived groups or projects not marked for deletion are returned. When set to false, only archived groups or projects marked for deletion are returned. If the parameter is undefined, no filtering is applied. This enhancement helps you efficiently manage your workflows by targeting specific statuses through simple API calls. Thank you @dagaranupam for adding this parameter to the Projects API.

Rate limits for Groups, Projects, and Users API

• Tier: Free, Silver, Gold
• Offering: GitLab.com
• Links: Documentation | Related issue We have added API rate limits for projects, groups, and users to improve platform stability and performance for all users. These changes are in response to increased API traffic that has been affecting our services. …