Gitlab Release Notes

On October 15, 2026, GitLab 19.5 was released with the following features.

We are excited to recognize Dhairya, a Level 3 contributor, as this month’s Notable Contributor!

Dhairya contributed to offline transfer and Organizations support for import, so that groups, projects, and their memberships can move between GitLab instances.

Primary features

GitLab MCP server is generally available

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, MCP clients could reach only a limited set of GitLab tools. Now the GitLab MCP server is generally available.

With the MCP server, any MCP-compatible agent, such as Claude Code or Cursor, gets direct access to the expanded GitLab catalog of tools and GitLab Duo Agent Platform agents and flows. Your agents can work across more of your GitLab workflow and run Agent Platform agents and flows without leaving your preferred tool.

GitLab Secrets Manager is generally available

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed
Add-ons: GitLab Secrets Manager
Links: Documentation · Related Issue

Without a centralized secrets store, credentials can become scattered across over-scoped CI/CD variables, local config files, and standalone vaults. This makes them harder to manage, protect, and audit.

GitLab Secrets Manager is now generally available on GitLab.com and GitLab Self-Managed. Built on OpenBao, it uses your existing group and project permissions, so there’s no separate access model to maintain. Each CI secret is scoped to the job that needs it, based on environment, branch, and branch protection rules. Audit logs are generated for every create, read, update, and delete.

GitLab Secrets Manager consumes GitLab Credits. Start a free 30-day trial or enable it for your group or instance.

Connect Externally Connected Agents (ECAs) to AI Governance

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Previously, the AI Governance Dashboard showed activity only from GitLab Duo Agent Platform agents. This provided you total visibility into all of your Agent Platform agents, including the sessions they were running, including tool calls, MCPs used, and the prompt input and output from the user and agent respectively.

With the GitLab 19.5 release, after a one-time glab govern setup, you can now extend governance visibility past just GitLab Duo Agent Platform agents, and connect Externally Connected Agents (ECAs) like Claude Code, Cursor, and Codex to GitLab AI Governance by using the GitLab CLI (glab).

When Allow external agents and Store AI audit events are enabled, security and compliance teams get visibility into ECAs that run outside GitLab, alongside your GitLab Duo Agent Platform agents. Every qualifying agent session is captured, including who ran it, which agent, which project, and when, with sessions and tool calls appearing in the AI Governance Dashboard and the AI audit events report. Audit events also flow to your SIEM through audit event streaming.

Tool output is not sent, except for short error messages from failed tool calls.

This feature is in beta. Share your feedback in issue 633489.

Non-default branch tracking generally available

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Non-default branch tracking is now generally available. You can 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 release includes the following capabilities:

• Track three additional branches or tags on the security configuration page. This is in addition to the default tracked branch.
• Filter by tracked ref on the vulnerability report.
• Filter by branch on the project-level security dashboard.
• Update vulnerability status on tracked branches.
• Vulnerability management policies evaluate each tracked branch separately and update only the vulnerabilities on that branch.

On GitLab Self-Managed, the tracked ref and branch filters require advanced vulnerability management.

Restrict GitLab Duo access by subgroup membership

Tier: Free, Premium, Ultimate
Offering: GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Administrators can now select any subgroup, not just top-level groups, in the Restrict access based on group membership setting for GitLab Duo. You can scope GitLab Duo Agent Platform access to a specific team or pilot group without restructuring your group hierarchy.

Previously, this setting accepted only top-level groups. Organizations with a single top-level group for all users had no supported way to limit GitLab Duo Agent Platform access to a subset of users.

Now, when you select a subgroup, direct members of that subgroup get access. This makes it easier to run a GitLab Duo Agent Platform pilot or roll out access one division at a time on GitLab Self-Managed and GitLab Dedicated.

Agentic Core

/goal command in GitLab Duo CLI is generally available

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

The /goal slash command in GitLab Duo CLI is now generally available in GitLab Duo CLI 9.27.0.

Describe an open-ended goal, and GitLab Duo delegates it to a governed, goal-driven flow that runs locally and handles both implementation and verification.

To start, run /goal <task>. For example:

/goal Fix the failing tests in spec/models/user_spec.rb

In GitLab 19.5 (GitLab Duo CLI 9.24.0), the Run suggested prompts as /goal sessions setting in /settings runs suggested prompts as /goal sessions instead of chat messages.

/goal requires GitLab 19.3 and later, and GitLab Duo CLI 9.17.0 and later.

Auto mode in GitLab Duo CLI

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

GitLab Duo CLI has a new auto mode.

In auto mode, GitLab Duo uses tools without asking for approval first, so longer tasks run without stopping for each shell command, git operation, or MCP tool call.

Auto mode respects your organization’s controls:

• Auto mode is off by default. Administrators, Owners, and Maintainers can turn the setting on for instances, groups, and projects.
• Administrators and group Owners can also lock it to Always off for the entire instance or group.
• Agent tool governance still applies. Tools set to Always Deny stay blocked.

To use auto mode, you need GitLab Duo CLI 9.22.0 or later.

Press Tab until the mode under the > prompt shows auto.

Use auto mode only in repositories you trust and on branches you can discard.

Configure GitLab Duo CLI with settings files

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

You can now configure GitLab Duo CLI with settings files, for yourself or for your whole organization.

The settings file stores the choices you make in the /settings panel.

You can also edit the file directly, or create it in advance, for example in a container image.

System administrators can deploy a managed settings file to each machine with a mobile device management tool or group policy.

Settings in the managed file take precedence over the settings file, command-line options, and environment variables, and users can’t change them.

Settings not in the managed file remain under user control.

The settings file requires GitLab Duo CLI 9.26.0 or later, and the managed settings file requires GitLab Duo CLI 9.27.0 or later.

Follow-up reviews in Code Review Flow

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, when you asked GitLab Duo to review a merge request again, it treated the review as a first pass. It could repeat findings from its earlier threads, even ones you had already addressed.

Now, Code Review Flow uses comment threads from earlier GitLab Duo reviews, including your replies, to evaluate new changes. GitLab Duo focuses on lines added after its last review, does not repeat points it already raised, and lists outstanding findings in its summary. If you reply on a thread to explain why the code is correct, GitLab Duo does not raise the point again.

To start a follow-up review, ask GitLab Duo to review the merge request again. With Start a new review on push turned on, GitLab Duo automatically starts a follow-up review when you push changes.

IAM roles for Amazon Bedrock self-hosted models

Tier: Premium, Ultimate
Offering: GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Previously, you could not control which AWS credentials the AI Gateway used for your Amazon Bedrock models. A single AWS identity needed access to all these models.

With this release, you can specify an IAM role for each model, and the AI Gateway assumes that role when calling the model. This way, each model gets only the AWS access it needs, even when the role is in another AWS account.

Improved first-run experience in GitLab Duo CLI

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

GitLab Duo CLI now helps new users get started without leaving the terminal:

• On first run, an onboarding card helps you connect MCP servers and install GitLab plugins.
• Each new session opens with prompts suggested from your open merge requests and issues.
• For a merge request prompt, GitLab Duo checks out the source branch first if it exists.
• The status bar shows your branch, project, merge request, /goal progress, and MCP status.
• The setup screen links to token creation and validates your token before saving.
• Tips in the prompt and the /whatsnew command point you to new features.

To get the full experience, update to GitLab Duo CLI 9.28.0 or later.

MCP server CI/CD artifact tool

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Previously, if you needed an agent to check something inside a CI/CD job’s build artifacts, it had to download and unzip the whole archive just to read one file. Now the get_artifact_file MCP tool lets your agent read a single file directly from a job’s artifacts, whether it’s a log, a generated report, or a test fixture.

MCP server GitLab Duo agent and flow tools

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

New GitLab Duo agent and flow tools let you invoke and track GitLab Duo agents and flows from any MCP client:

• start_duo_session starts a session.
• get_duo_session reads a session’s current state.
• list_duo_sessions pages through your session history.
• list_duo_agents_and_flows lists the GitLab Duo agents and flows enabled in a project.

MCP server groups tool

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Previously, an agent connecting to GitLab over MCP had no way to discover which groups and subgroups you have access to without you hardcoding IDs or paths. The new list_groups tool lets your agent browse your organization’s group hierarchy on its own, so it can find the right group before acting instead of guessing at identifiers.

MCP server toolset selection

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

You can now choose which toolsets the GitLab MCP server exposes. Every additional tool that isn’t required wastes space in the LLM’s context window, and runs the risk of confusing the LLM, especially if you are using multiple MCP servers at once.

New Agentic Chat UI generally available in IDEs

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

The redesigned GitLab Duo Agentic Chat UI in VS Code and JetBrains IDEs, introduced as a beta in GitLab 19.3, is now generally available and is the default layout.

You no longer need to turn on beta and experimental features to use it.

The new layout has no tabs. You start conversations, view your chat history, and select an agent and model in the same view.

The new layout is the default in:

• GitLab for VS Code 7.2.0 and later
• GitLab Duo plugin for JetBrains IDEs 3.50.0 and later

To use the Software Development Flow or view the flows you have run, switch to the classic layout from the panel.

New rate limits for GitLab MCP server

Tier: Free, Premium, Ultimate
Offering: GitLab.com
Links: Documentation · Related Issue

If you connect an agent to GitLab over MCP today, nothing stops it from reconnecting or retrying faster than your workflow actually needs, and on GitLab.com that carries a cost.

Starting October 15, the GitLab MCP server on GitLab.com limits each user to 60 requests a minute on the Free tier and 600 on Premium and Ultimate. Every reconnect and retry counts toward your limit. If your agent starts getting rate-limited (HTTP 429) errors, check its reconnect and retry settings before upgrading to a higher tier.

Provide images as context for Developer Flow and Agentic Chat in your IDE

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, the Developer Flow and Agentic Chat could only read text, so a screenshot on a bug report or a diagram in a design discussion never reached the model. Now the Developer Flow, including when you start it from Agentic Chat, and Agentic Chat in your IDE can read images in your repository and attachments on issues, merge requests, and comments in the same project, and use them as context.

You cannot upload an image directly in your prompt. Instead, name an image that already exists, by its file path in the repository or by its upload reference. For details, see the documentation.

Recommend reviewers with GitLab Duo

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, you had to check each approval rule and guess who had time to review your merge request. Or you assigned a whole group and hoped someone picked it up.

Now you can use the Recommend Reviewers Flow to suggest reviewers instead. The flow is generally available.

For each approval rule, it recommends the minimum number of reviewers needed, based on availability, workload, time zone, and recent activity.

Recommendations appear in the Recommended section of the merge request sidebar. Hover over a user to see why they were recommended.

To get started, turn on the flow for your top-level group. It runs when a merge request is created, or you can create a trigger to run it when a draft is marked ready. To get new recommendations, select Refresh.

Software Development Flow requires updated IDE extensions

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

The Software Development Flow now runs on the GitLab Duo Agent Platform flow registry, the same foundation as other flows.

The flow works the same way in your IDE, and new fixes and improvements go to this version.

To keep using the Software Development Flow, update your editor extension to one of these versions or later:

• GitLab for VS Code 6.85.0
• GitLab Duo plugin for JetBrains IDEs 3.40.0
• GitLab for Visual Studio 0.79.0

Trigger flows with a generally available API

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, the API endpoint you use to trigger GitLab Duo Agent Platform flows from CI/CD pipelines, scripts, and other automation was an experiment, so it was hard to know whether you could rely on it in production.

Now the trigger a flow endpoint of the Flows API is generally available, so you can build production automation on it knowing it follows the GitLab REST API breaking changes policy.

Unified DevOps and Security

Child pipelines can depend on parent jobs optionally

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Many development teams split large CI/CD setups into parent and child pipelines so each part is easier to manage.

Until now, a child pipeline job couldn’t safely depend on a parent job that only runs under certain conditions, such as tests that run only when certain files change. If that parent job was skipped, the child job broke, so teams had to work around it with duplicate jobs or brittle scripts.

Now you can mark these dependencies as optional. If the parent job runs, the child waits for it as usual. If it doesn’t run, the child job goes ahead without it. Pipelines stay fast and reliable without the workarounds, and a failure in a job that does run still stops the pipeline, so quality checks aren’t weakened.

Thank you to Jimmy Spagnola for this contribution!

Customize security configuration profiles

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

You can now customize Secret Detection and SAST profiles in the UI. Set scan options like excluded paths, custom analyzer images, and full Git history scans once for a group, and apply them to all its projects.

Previously, a security configuration profile enabled a scanner with its default settings. Anything beyond the defaults required edits to .gitlab-ci.yml in each project. Now the profile includes those settings too.

Currently, customization of Dependency Scanning profiles is only available through the GraphQL API. UI customization is planned in a future release.

Embed code from a repository in Markdown

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

In previous versions of GitLab, permalinks to a file’s lines rendered as plain URLs, so you had to leave the merge request, issue, or wiki page to view the referenced code.

Now, permalinks render as a syntax-highlighted snippet with the file path and commit, so you can read the code without leaving the page. You can only view embedded snippets if you have read access to the repository.

GitLab Observability is now in beta

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed
Links: Documentation · Related Issue

In previous versions of GitLab, Observability was an experiment. Now it’s in beta on GitLab.com and GitLab Self-Managed.

With GitLab Observability, you can send traces, metrics, and logs with OpenTelemetry, then explore them next to your code, merge requests, and CI/CD pipelines.

On GitLab.com, each group or personal namespace opts in by selecting Enable Observability.

On GitLab Self-Managed, you host the Observability backend and connect it to a group or personal namespace.

Observability is available at no cost during the beta.

Sort Markdown tables by column

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

In previous versions of GitLab, to find information in a large Markdown table, you had to scan every row or copy the table into a spreadsheet.

Now you can sort rendered Markdown tables by any column, in both view mode and preview.

In a column header, select the sort button to sort rows in ascending or descending order, then reset to restore the original order. You can also sort with a keyboard.

Sticky headers for Markdown tables

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

In previous versions of GitLab, when you scrolled through a long table, the header row scrolled out of view, so it was hard to tell what each column contained.

Now, table headers stay visible at the top of the table as you scroll, in view mode, preview, and the rich text editor. Sticky headers are always on, so you don’t need to change any settings.

Accurate merge request security report comparisons

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, if a scan had more than 25 findings of one severity, the security report compared only 25 of them from each pipeline. Unchanged findings could appear as new or fixed.

Now, the report compares up to 1,000 findings per severity, so the new and fixed lists are more accurate.

AI flows supported on non-default branches

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, you could run the SAST False Positive Detection, SAST Vulnerability Resolution, and Secret False Positive Detection flows only on vulnerabilities in the default branch.

Now, you can also run these flows on vulnerabilities in other tracked branches from the vulnerability report to analyze and resolve them before you merge.

Business Logic Security Analyzer (closed beta)

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

Business Logic Security Analyzer is a GitLab Duo Agent Platform foundational flow that reasons about what your code is meant to enforce. It finds vulnerabilities that pattern-based scanners often miss: broken object-level authorization, missing authorization checks, and mass assignment.

Start a whole-repository scan from GitLab Duo Chat or the API. To scan merge requests automatically, attach the Business Logic scan profile to a project. Findings appear in the vulnerability report and the merge request security widget.

Business Logic Security Analyzer is in closed beta for GitLab Ultimate customers on GitLab.com. To request access, contact your account team. Each scan consumes GitLab Credits. For prerequisites and setup, see Business logic scanning.

GitLab Relay (KAS) connections default to gRPC

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

GitLab Relay (KAS) now uses gRPC by default. GitLab.com advertised grpcs://kas.gitlab.com in GitLab 19.4. In GitLab 19.5, new Linux package and Helm chart installations advertise grpcs:// too. New agent installations connect over grpcs:// instead of gRPC wrapped in WebSocket, which means one protocol to route and troubleshoot, and less overhead for each connection.

Agents that already connect over wss:// work, but you should move them.

On GitLab.com, set the agent address to grpcs://kas.gitlab.com. For example, use --set config.kasAddress=grpcs://kas.gitlab.com when you upgrade the gitlab-agent Helm chart. On GitLab Self-Managed, use the address shown in the agent installation command after you upgrade.

GitLab Runner 19.5

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

We’re also releasing GitLab Runner 19.5 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

• Clearer Kubernetes executor error message when the helper container is OOM-killed
• Log the CPU model of the job execution environment at job start

Bug Fixes

• IPv4-only services fail on dual-stack networks because Docker service health check dials only the last resolved address
• Runner and job tokens with an instance prefix are not recognized
• Kubernetes executor sends an unpaginated events LIST request on every poll, saturating API Priority and Fairness on busy clusters
• Docker executor applies mac_address to service containers instead of only the build container
• RUNNER_AFTER_SCRIPT_TIMEOUT is reset to 5 minutes when it exceeds the job timeout
• Cache upload fails with 403 on S3 servers that enforce SigV4 signed-header rules because cache_archiver sends a Content-Type the presigned URL does not sign
• Kubernetes executor always sets an empty pod-level resources object, causing BestEffort QoS misclassification on Kubernetes 1.34 and later
• Step-runner local server reports ready before its gRPC server is listening
• Documented systemd graceful shutdown configuration kills the running VM for the VirtualBox, Parallels, and SSH executors
• proxy_exec prints the helper binary help and exits instead of running the job when the image has a multi-argument ENTRYPOINT
• Docker executor ignores the platform parameter when multiple platforms of the same image are pulled

The list of all changes is in the GitLab Runner CHANGELOG.

Share filtered views of the security inventory

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

You can now share a filtered view of the security inventory with a link. Filter by tool coverage, vulnerability count, or project name, then copy the URL and send it. Whoever opens the link sees the same view.

Previously, only the project name search was saved in the URL, so a shared link lost the other filters. Now the full filter state is preserved, so you can bookmark a view or hand it to the team that owns those projects.

Scale and Deployments

Start a custom flow in GitLab Duo Agentic Chat

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

You can now start a custom flow directly from GitLab Duo Agentic Chat, without needing to configure a trigger first.

Previously, running a custom flow required setting up a trigger event — a mention, an assignment, or similar — which made flows difficult to test and iterate on. Now, you can launch any AI Catalog flow enabled in your project by sending a message in GitLab Duo Agentic Chat. Your message becomes the goal for the flow. If you send no goal, the flow falls back to its own description.

Chat links to the resulting agent session so you can follow along.

See your own GitLab Credits usage

Tier: Premium, Ultimate
Offering: GitLab.com
Links: Documentation · Related Issue

If you used GitLab Credits, you had no way to check your own usage.

Only group Owners and administrators could open the GitLab Credits dashboard, so you had to ask someone with access.

You can now see your own usage in User settings > GitLab Credits. The page shows your total usage, daily average, and peak day, and you can filter by product or select a date range. If you belong to more than one group with GitLab Credits, you can switch between them.

Co-created contributions

Resync an LDAP-blocked user on demand

Tier: Free, Premium, Ultimate
Offering: GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Administrators can now resync a single LDAP-blocked user from the Admin area Users page. The new Resync with LDAP action runs an LDAP access check and unblocks the user when LDAP allows access, or leaves the user blocked when it does not. If the user has no LDAP identity, the action declines with a message. In previous versions of GitLab, an LDAP-blocked account stayed blocked until the daily user sync ran or the user signed in, which service accounts cannot do.

Thank you to Sergey Pechenko for this contribution (MR)!

Cancel auto-merge from the REST API

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

You can now cancel an active auto-merge with the cancel_auto_merge API endpoint. If the merge request is on a merge train, the call also removes it from the train. The older cancel_merge_when_pipeline_succeeds endpoint is now deprecated.

Separately, git push -o merge_request.auto_merge is now rejected with a remote message when you cannot merge to the target branch. In previous versions of GitLab, the auto-merge was recorded and left the merge request unmergeable until canceled.

Thank you to the following users for these contributions!

• José M. Requena Plens (MR 1 MR 2)
• Bobby Nandigam (MR)

Configure job log update frequency

Tier: Free, Premium, Ultimate
Offering: GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Administrators can now set how often job logs update, under Admin area > Settings > CI/CD or through the Settings API. You can select between 3 to 3600 seconds.

In previous versions of GitLab, these intervals were constants, so you could not shorten the initial live-log delay for short jobs without patching the instance.

Thank you to Aleksandr Kotlyar for this contribution (MR)!

Repository tags and Terraform states in GraphQL

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

GraphQL now exposes Repository.tags, with forward pagination, search, and a TagSort enum for name, updated, and version order, at up to 100 tags per page. Repository.tags is an experiment in GitLab 19.5. TerraformState.versions lists a state’s versions, newest first.

The merge requests REST API now returns author.bot on single and list responses, so a client can tell bot and service account authors apart without a second call.

Thank you to the following users for these contributions!

• Jeston Singh (MR 1 MR 2)
• Ivane Gkomarteli (MR)

Commit count variable in commit templates

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

You can now use %{commits_count} in merge commit and squash commit message templates, and in new merge request description templates. For example, %{title} (%{commits_count} commits) renders as Bugfix (3 commits).

Thank you to Jeston Singh for this contribution (MR)!

Submit a review to become a reviewer

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

When you submit a review on a merge request you are not yet a reviewer of, with Comment, Approve, or Request changes, GitLab now adds you to the Reviewers list. The review drawer tells you beforehand: “You will be added as a reviewer.” The Reviewers list and the people who took part in the review no longer drift apart. This behavior has been available since GitLab 19.4, when its feature flag was removed.

Thank you to Michael Fischer for this contribution (MR)!

Revoked GPG identities no longer verify commits

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

GitLab now ignores user IDs that GPG reports as revoked. A revoked identity no longer appears under Access > GPG keys in user settings and no longer counts as a verified email for the Verified badge on signed commits. Commits signed under a revoked identity move to “same user, different email” or “other user”, and a key whose every identity is revoked verifies nothing. Signatures already verified under a key that stays in place are not re-derived.

Thank you to José M. Requena Plens for this contribution (MR)!

Other improvements

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Other improvements in this release include:

• GitLab MCP server: rate-limited tool results name the limit and retry delay, add_branch returns the branch web_url, tool aliases in the enabled-tools header resolve, mismatched URL and project ID inputs are rejected, and ai_workflows tokens can read blobs in batch.
• Administrators in admin mode can set a cluster agent on an environment without joining the project.
• CI_JOB_TAGS and CI_RUNNER_TAGS JSON-encode each tag. Duplicate variable keys in push options are rejected.
• Advanced SAST (Ultimate): C and C++ files up to 20 levels deep are scanned, and the report follows your artifact retention.
• Plain-text token and SSH key emails link to the right page, and ?scopes= links prefill the token form.

Thank you to the following users for these contributions!

• otutukingsley (MR)
• Jeston Singh (MR 1 MR 2 MR 3 MR 4 MR 5 MR 6)
• ryo-whaletech (MR 1 MR 2 MR 3)
• Mohamed Elsayed (MR)
• Gerardo Navarro (MR)
• Torben Buck (MR 1 MR 2 MR 3)

Other additions to the interface

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Other additions to the interface in this release include:

• Changing Approvals required in merge request settings shows a toast on success and an alert on failure.
• A compliance framework whose requirement already has 5 controls can be edited again.
• A failed protected environment update shows the API message.
• In the Create branch dialog, the submit button stays disabled until the branch name is validated.
• Archived labels show an Archived tooltip in issue and merge request lists, and cannot be newly assigned.
• SCIM tokens cannot be generated while the group’s SAML provider is disabled.
• .4dm files are syntax highlighted.
• Right-aligned Markdown table columns use fixed-width numerals.
• Approval rules, compliance frameworks, and protected environments require Premium or Ultimate.

Thank you to the following users for these contributions!

• Sahil Bhatt (MR 1 MR 2)
• Jeston Singh (MR)
• Vladislav Petrov (MR)
• Nicholas Wittstruck (MR)
• ryo-whaletech (MR)
• Sergey Pechenko (MR)
• Logan Swartzendruber (MR)
• Steve Mokris (MR)

Original source

On October 12, 2026, we released versions 19.4.2, 19.3.5, 19.2.8 for GitLab Community Edition (CE) and Enterprise Edition (EE).

19.3.4 had a bug that affected merge request pages when the Ona integration was enabled. This is fixed in 19.3.5.

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.

All GitLab Dedicated tenants were patched using an internal release before this patch release was published.

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

Title Severity Integer Overflow issue in CI/CD Regular Expression Compiler impacts GitLab CE/EE Critical Cross-site Scripting issue in syntax highlighting impacts GitLab CE/EE High Improper Authorization issue in downstream pipeline creation service impacts GitLab CE/EE High Permissive Regular Expression issue in repository file access impacts GitLab CE/EE High Incorrect Authorization issue in scheduled pipeline execution policy impacts GitLab EE High Improper Neutralization of Input Used for LLM Prompting issue in GitLab Duo Agent Platform impacts GitLab EE High Sensitive Information Exposure issue in GitLab Pages impacts GitLab CE/EE Medium Open Redirect issue in Kubernetes proxy impacts GitLab CE/EE Medium Incorrect Authorization issue in GraphQL notes widget impacts GitLab CE/EE Medium Incorrect Authorization issue in GraphQL work item hierarchy impacts GitLab CE/EE Medium Incorrect Authorization issue in GraphQL scope impacts GitLab CE/EE Medium Page cache poisoning via improper cache key construction in merge requests impacts GitLab CE/EE Medium Incorrect Authorization issue in work items GraphQL API impacts GitLab CE/EE Medium Missing Authorization issue in merge request accessibility report comparison endpoint impacts GitLab CE/EE Medium Incorrect Privilege Assignment issue in custom roles impacts GitLab EE Medium Insufficient Granularity of Access Control issue in project label management impacts GitLab CE/EE Medium Governance Control Bypass issue in Duo Agent Platform impacts GitLab EE Medium Incorrect Authorization issue in package registry impacts GitLab CE/EE Medium Incorrect Authorization issue in merge request approval eligibility check impacts GitLab EE Medium Incorrect Authorization issue in fine-grained personal access tokens impacts GitLab CE/EE Medium Server Side Request Forgery (SSRF) issue in repository import impacts GitLab CE/EE Low Incorrect Authorization issue in project import impacts GitLab CE/EE Low Incorrect Authorization issue in Package Registry impacts GitLab CE/EE Low Improper Access Control issue in project CI/CD settings impacts GitLab EE Low

CVE-2026-97229 - Integer Overflow issue in CI/CD Regular Expression Compiler impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary code on the GitLab server via a specially crafted regular expression in a CI/CD configuration, due to insufficient regular expression validation.

Impacted Versions: GitLab CE/EE: all versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 10.0 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H)

Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-92883 - Cross-site Scripting issue in syntax highlighting impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user to execute arbitrary JavaScript in the context of other users’ browser sessions via a specially crafted repository, due to improper sanitization of HTML attributes in syntax-highlighted output.

Impacted Versions: GitLab CE/EE: all versions from 19.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 8.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N)

Thanks a0xnirudh for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-16301 - Improper Authorization issue in downstream pipeline creation service impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user with Developer role to execute CI/CD pipelines on protected branches without authorization due to improper authorization checks in the downstream pipeline creation service.

Impacted Versions: GitLab CE/EE: all versions from 18.7 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 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-14814 - Permissive Regular Expression issue in repository file access impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed a user to poison cached responses for raw repository files, causing targeted users’ CI/CD pipelines to execute specially crafted content and potentially exposing protected environment variables, due to improper validation of repository references.

Impacted Versions: GitLab CE/EE: all versions before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 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-81839 - Incorrect Authorization issue in scheduled pipeline execution policy impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user to execute arbitrary CI/CD pipelines in a transferred project with the new group’s privileges due to improper cleanup of scheduled pipeline execution policy records.

Impacted Versions: GitLab EE: all versions from 18.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 7.7 (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N)

Thanks no_01 for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-96893 - Improper Neutralization of Input Used for LLM Prompting issue in GitLab Duo Agent Platform impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user to inject specially crafted content into AI agent instructions, potentially causing unintended command execution attributed to other users, due to improper neutralization of special elements in AI conversation context construction.

Impacted Versions: GitLab EE: all versions from 19.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 7.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N)

This vulnerability has been discovered internally by GitLab team member Mert Coskuner.

CVE-2026-101168 - Sensitive Information Exposure issue in GitLab Pages impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user with access to GitLab Pages log data to obtain access tokens and other secrets, due to insertion of sensitive request data into log files and error tracking events.

Impacted Versions: GitLab CE/EE: all versions from 12.0 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 6.2 (CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N)

This vulnerability has been discovered internally by GitLab team member RJ Coleman.

CVE-2026-7767 - Open Redirect issue in Kubernetes proxy impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user controlling a Kubernetes agent to cause sensitive authentication tokens to be sent to an unintended server due to improper redirect validation in the Kubernetes proxy.

Impacted Versions: GitLab CE/EE: all versions from 13.11 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 5.8 (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N)

Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-16275 - Incorrect Authorization issue in GraphQL notes widget impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an unauthenticated user to read confidential notes on public projects due to incorrect authorization checks.

Impacted Versions: GitLab CE/EE: all versions from 17.4 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)

Thanks jaykp for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-84284 - Incorrect Authorization issue in GraphQL work item hierarchy impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an unauthenticated user to read work item contents from private groups and projects due to incorrect authorization checks.

Impacted Versions: GitLab CE/EE: all versions from 17.11 before 19.2.8, all 19.3 versions, and 19.4 before 19.4.2

CVSS 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-85529 - Incorrect Authorization issue in GraphQL scope impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an unauthenticated user to read internal notes and confidential system notes on public projects due to improper authorization in the GraphQL API.

Impacted Versions: GitLab CE/EE: all versions from 19.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)

Thanks silaen_space for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-100755 - Page cache poisoning via improper cache key construction in merge requests impacts GitLab CE/EE

GitLab has remediated an issue that, under certain deployment configurations, could have allowed an authenticated user to poison cached page content served to other users due to improper cache key construction.

Impacted Versions: GitLab CE/EE: all versions from 16.2 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 4.6 (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:L)

This vulnerability has been discovered internally by GitLab team member Peter Arts.

CVE-2026-14552 - Incorrect Authorization issue in work items GraphQL API impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user with Guest access to read confidential epic content meant to be restricted by external authorization, due to incorrect authorization checks.

Impacted Versions: GitLab CE/EE: all versions from 17.0 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N)

Thanks 3nvz for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-6567 - Missing Authorization issue in merge request accessibility report comparison endpoint impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user with reporter role to access restricted CI artifact report content they were not authorized to, due to missing authorization checks.

Impacted Versions: GitLab CE/EE: all versions from 13.8 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N)

Thanks se1en for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-104661 - Incorrect Privilege Assignment issue in custom roles impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user holding a custom role with compliance framework administration permissions to configure and execute a specially crafted compliance pipeline across group projects due to improper privilege assignment.

Impacted Versions: GitLab EE: all versions from 17.0 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 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 a GitLab team member.

CVE-2026-14210 - Insufficient Granularity of Access Control issue in project label management impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user with a project-scoped fine-grained Personal Access Token to permanently delete or modify group-level labels, due to incorrect authorization logic on label ownership scope validation.

Impacted Versions: GitLab CE/EE: all versions from 18.11 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N)

Thanks bate5a for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-105458 - Governance Control Bypass issue in Duo Agent Platform impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user holding a specific granular permission to obtain a GitLab Duo Agent Platform token that bypasses governance controls, due to reliance on untrusted input in a security decision.

Impacted Versions: GitLab EE: all versions from 19.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 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 Rahul Barnwal.

CVE-2026-5954 - Incorrect Authorization issue in package registry impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed a user to download package files from a public project due to improper authorization checks.

Impacted Versions: GitLab CE/EE: all versions from 15.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 4.2 (CVSS:3.1/AV:N/AC:H/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-92528 - Incorrect Authorization issue in merge request approval eligibility check impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user to approve a merge request despite having contributed commits to it, due to improper identity resolution.

Impacted Versions: GitLab EE: all versions from 16.11 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 4.2 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N)

This vulnerability has been discovered internally by GitLab team member Kenneth Chu.

CVE-2026-78335 - Incorrect Authorization issue in fine-grained personal access tokens impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user holding a project-scoped fine-grained Personal Access Token to modify integrations belonging to a group outside the token’s scope, due to incorrect authorization checks.

Impacted Versions: GitLab CE/EE: all versions from 19.1 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 4.2 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N)

Thanks mahoraga007 for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-100104 - Server Side Request Forgery (SSRF) issue in repository import impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user to perform server-side request forgery and reach internal network resources due to a time-of-check to time-of-use race condition in URL validation during repository import operations.

Impacted Versions: GitLab CE/EE: all versions from 10.3 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 3.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N)

This vulnerability has been discovered internally by GitLab team member Félix Veillette-Potvin.

CVE-2026-82632 - Incorrect Authorization issue in project import impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user with a fine-grained Personal Access Token scoped only to user-boundary import permissions to import projects into group namespaces beyond the token’s intended scope, due to incorrect authorization of the import target namespace.

Impacted Versions: GitLab CE/EE: all versions from 18.9 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 3.1 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N)

Thanks aur0r4_glyph for reporting this vulnerability through our HackerOne bug bounty program.

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

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user with maintainer-role permissions to remove certain package registry metadata that package protection rules restrict to higher roles, due to improper authorization checks.

Impacted Versions: GitLab CE/EE: all versions from 17.6 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 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 a GitLab team member.

CVE-2026-9268 - Improper Access Control issue in project CI/CD settings impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user with limited permissions to modify project CI/CD deployment rollback settings without proper authorization, due to insufficient access control checks.

Impacted Versions: GitLab EE: all versions from 13.6 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2

CVSS 2.7 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N)

Thanks akashhamal0x01 for reporting this vulnerability through our HackerOne bug bounty program.

Bug fixes

19.4.2

• Install tzdata and tzdata-legacy in gitlab-base
• Add Ruby regexp program size patch for 3.3 and 3.4 [19.4]
• Add Ruby regexp repeat-range double-free patch for 3.3 and 3.4 [19.4]
• Backport of ‘Add rate limit handling to imports from GHES’ to 19.4
• Backport of ‘Retry transient HttpIO chunk failures’ (19.4)
• Backport of “Fix any_merge_request policy violations stuck in running on fork MRs”
• Backport of ‘Update dependency gitlab-fog-azure-rm to v2.5.2’ to 19-4
• Backport of “Verify legacy uploads on Geo secondaries by reading the file”
• Backport 19.4 What’s new entries to 19.4 stable branch
• Backport of ‘Make git exclusions in rate limit rules unconditional again’ into 19-4-stable-ee
• Backport of ‘Fix work item status category not updating when a status is re-added’
• Backport of ‘Fix status filter dropping matching items’
• Backport of “DAP flow execution image: registry prefix with path (e.g., Harbor proxy) treated as full image reference”
• Truncate Jira issue keys at the per-entity API limit (19.4)
• Backport of Sign chat agent requests from the chat feature setting and Sign chat tool requests from the resolved feature setting to 19.4
• Backport of ‘Serve the Orbit MCP server without the mcp_client feature flag’ to 19.4
• Backport of ‘Speed up assignee and reviewer pickers for Duo service accounts’
• Backport of ‘Stop coverage delta timeouts from breaking the MR widget’
• Backport of ‘Fix file tree links missing relative URL root’ to 19.4
• Backport of ‘Align self-managed Restricted access with User.billable’
• Backport of ‘Send canonical timezone identifiers to Gitaly’
• Backport of ‘Authenticate self-hosted billing events with CustomersDot token’ to 19.4
• Backport 19.4: Tolerate malformed Content-Range in HttpIO
• Backport of ‘Fix file tree search missing relative URL root’ to 19.4
• Backport of ‘Allow security policy bot cross-project container registry access’ to 19.4
• Backport of ‘Fix Gitaly up-to-date check for versions with a Git revision suffix’
• Fix registry DB migration log accumulation
• Add Ruby regexp program size patch for 3.3 and 3.4 [19.4]
• Add Ruby regexp repeat-range double-free patch for 3.3 and 3.4 [19.4]

19.3.5

• Bump ElasticSearch version
• Add Ruby regexp program size patch for 3.3 and 3.4 [19.3]
• Add Ruby regexp repeat-range double-free patch for 3.3 and 3.4 [19.3]
• Backport of ‘Resolve orphan artifact lookups in one query per batch’
• Backport of ‘Specify low urgency of getPipelineDetails query’ to 19.3
• 19.3 Backport of ‘Remove merge_request from Developer default triggers’
• Backport ‘Drop system failure assertion in secrets specs’ to 19-3-stable-ee
• Backport of ‘Stop dependency proxy requests counting against the web rate limit’
• Backport of ‘Update GitLab Elasticsearch Indexer to 5.14.14’ to 19.3
• Backport of ‘Add application setting to block JWT for reclaimed project paths’
• Backport of ‘Resume mid-delta on the package metadata label path’ into 19-3-stable-ee
• Backport of ‘Retry transient HttpIO chunk failures’ (19.3)
• Backport of ‘Update dependency gitlab-fog-azure-rm to v2.5.2’ to 19-3
• Backport of “Verify legacy uploads on Geo secondaries by reading the file”
• Backport of ‘Make git exclusions in rate limit rules unconditional again’ into 19-3-stable-ee
• Backport of ‘Delete approval policy reads before their project rules’ and two related orphaned-read fixes to 19.3
• Backport of ‘Batch the push commit overlap lookup in RefreshService’ (19.3)
• Backport of ‘Skip the post-merge diff commit preload in RefreshService’ (19.3)
• Backport of ‘Fix work item status category not updating when a status is re-added’
• Backport of ‘Fix status filter dropping matching items’
• Backport of ‘Serve the Orbit MCP server without the mcp_client feature flag’ to 19.3
• Backport of “DAP flow execution image: registry prefix with path (e.g., Harbor proxy) treated as full image reference”
• Backport of Sign chat agent requests from the chat feature setting and Sign chat tool requests from the resolved feature setting to 19.3
• Backport of ‘Speed up assignee and reviewer pickers for Duo service accounts’
• Truncate Jira issue keys at the per-entity API limit (19.3)
• Backport of ‘Stop coverage delta timeouts from breaking the MR widget’
• Backport of ‘Align self-managed Restricted access with User.billable’
• Backport of ‘Fix file tree links missing relative URL root’ to 19.3
• Backport 19.3: Tolerate malformed Content-Range in HttpIO
• Backport of ‘Fix file tree search missing relative URL root’ to 19.3
• Fix incorrect merge_request variable name
• Fix registry DB migration log accumulation
• Bumps Elastic Search version
• Add Ruby regexp program size patch for 3.3 and 3.4 [19.3]
• Add Ruby regexp repeat-range double-free patch for 3.3 and 3.4 [19.3]

19.2.8

• Add Ruby regexp program size patch for 3.3 and 3.4 [19.2]
• Add Ruby regexp repeat-range double-free patch for 3.3 and 3.4 [19.2]
• Backport of ‘Update dependency gitlab-fog-azure-rm to v2.5.2’ to 19-2
• Backport of “Verify legacy uploads on Geo secondaries by reading the file”
• Backport of ‘Delete approval policy reads before their project rules’ and two related orphaned-read fixes to 19.2
• Backport of ‘Fix work item status category not updating when a status is re-added’
• Truncate Jira issue keys at the per-entity API limit (19.2)
• Backport of ‘Fix status filter dropping matching items’
• Backport of Sign chat agent requests from the chat feature setting and Sign chat tool requests from the resolved feature setting to 19.2
• Backport of ‘Fix file tree links missing relative URL root’ to 19.2
• Backport of ‘Align self-managed Restricted access with User.billable’
• Backport 19.2: Tolerate malformed Content-Range in HttpIO
• Backport of ‘Fix file tree search missing relative URL root’ to 19.2
• Fix registry DB migration log accumulation
• Add Ruby regexp program size patch for 3.3 and 3.4 [19.2]
• Add Ruby regexp repeat-range double-free patch for 3.3 and 3.4 [19.2]

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.3.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.

Original source

We have released versions 19.2.4, 19.3.2, and 19.4.1 of the GitLab AI Gateway.

These versions contain a critical security fix for GitLab Self-Hosted AI Gateway, and we strongly recommend that all GitLab Self-Managed customers with GitLab Self-Hosted AI Gateway installations update to one of these versions immediately. We have conducted targeted outreach to Self-Hosted AI Gateway customers prior to this release post with this guidance.

A fix has already been deployed for GitLab-hosted AI Gateways. Customers using GitLab.com, GitLab Dedicated, and GitLab Self-Managed instances using a GitLab-hosted AI Gateway are protected and do not need to take action.

Recommended Action

We strongly recommend that all GitLab Self-Hosted AI Gateway installations running a version affected by the issue described below are upgraded to one of the patched versions listed above as soon as possible.

Security fixes

Table of security fixes

Title Severity Improper Neutralization issue in custom flow prompt template impacts AI Gateway Critical

CVE-2026-90970 - Improper Neutralization issue in custom flow prompt template impacts AI Gateway

GitLab has remediated an issue in the GitLab AI Gateway that, under certain conditions, could have allowed an authenticated user with Duo Agent Platform access to escape the prompt template sandbox via a specially crafted flow configuration, leading to arbitrary command execution on the AI Gateway.

Impacted Versions: GitLab AI Gateway: all versions from 18.1.6 before 19.2.4, 19.3 before 19.3.2, and 19.4 before 19.4.1

CVSS 9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H)

Thanks invisiblemeerkat for responsibly disclosing this issue.

Updating

To update GitLab Self-Hosted AI Gateway, see the GitLab Self-Hosted AI Gateway install documentation.

Receive Patch Notifications

To receive release notifications via RSS, subscribe to our patch release RSS feed or our RSS feed for all releases.

Original source

On September 23, 2026, we released versions 19.0.9 and 18.11.12 for GitLab Community Edition (CE) and Enterprise Edition (EE).

These versions backport the fixes for two critical vulnerabilities, CVE-2026-85706 and CVE-2026-87719, that were originally patched in 19.3.2, 19.2.6, and 19.1.8 on September 10, 2026. These backports were made available outside of our standard maintenance policy so that self-managed administrators running 18.11 and 19.0 can apply the fixes without first completing a version upgrade. These versions contain no other changes.

We strongly recommend that all self-managed GitLab installations still running 18.11 or 19.0 be upgraded to one of these versions immediately. Installations running 19.1, 19.2, or 19.3 should upgrade to 19.1.8, 19.2.6, or 19.3.2 or later instead. 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 GitLab release blog posts.

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

The fixes in these versions are the same fixes that were released in 19.1.8, 19.2.6, and 19.3.2 on September 10, 2026.

Table of security fixes

Title Severity Path Traversal issue in repository commits API impacts GitLab CE/EE Critical Insecure Deserialization issue in GraphQL subscription serializer impacts GitLab EE Critical

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 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2

CVSS 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.

Detecting CVE-2026-85706 Exploitation Attempts

CVE-2026-85706 has been added to CISA’s Known Exploited Vulnerabilities catalog. GitLab-managed infrastructure, including GitLab.com and GitLab Dedicated, remains patched. GitLab security has released three threat detections to support customers with self-managed instances:

• GitLab LFI attempt reading gitlab.yml
• GitLab LFI via metadata.path parameter
• GitLab LFI file path attempt

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 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2

CVSS 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.

Bug fixes

These versions contain the security fixes listed above only. They do not contain any other bug fixes.

Important notes on upgrading

19.0.9 and 18.11.12 are backport releases for self-managed installations that cannot immediately move to a supported 19.1 or later version. Upgrading to the latest supported version remains the recommended path, because 18.11 and 19.0 do not receive the other fixes included in 19.1.8, 19.2.6, and 19.3.2.

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.

Original source

On September 23, 2026, we released versions 19.4.1, 19.3.3, 19.2.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

Title Severity Double Free issue in Regular Expression Parser impacts GitLab CE/EE Critical Integer Overflow issue in Regular Expression Compiler impacts GitLab CE/EE Critical Cross-site Scripting issue in merge request diff viewer impacts GitLab CE/EE High Missing Authorization issue in Duo AI job troubleshooting feature impacts GitLab EE High Incorrect Authorization issue in MCP API scope enforcement impacts GitLab CE/EE Medium Use of Less Trusted Source issue in Direct Transfer import user mapping impacts GitLab CE/EE Medium Missing Authorization issue in Epic Issues REST API impacts GitLab CE/EE Medium Incorrect Authorization issue in Duo Workflow Service token governance enforcement impacts GitLab EE Medium Improper Access Control issue in GraphQL memberRoles dependentSecurityPolicies resolver impacts GitLab EE Medium Missing Authorization issue in GraphQL CI job trace API impacts GitLab CE/EE Low Race Condition issue in MCP gitlab_search tool impacts GitLab CE/EE Low

CVE-2026-89078 - Double Free issue in Regular Expression Parser impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to execute arbitrary code on the GitLab server due to a double free issue when parsing a specially crafted regular expression in a CI/CD configuration.

Impacted Versions: GitLab CE/EE: all versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1

CVSS 9.9 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L)

Thanks joaxcar for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-93577 - Integer Overflow issue in Regular Expression Compiler impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to execute arbitrary code on the GitLab server due to an integer overflow issue when compiling a specially crafted regular expression in a CI/CD configuration.

Impacted Versions: GitLab CE/EE: all versions from 19.2 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1

CVSS 9.9 (CVSS:3.1/AV:N/AC:L/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-84739 - Cross-site Scripting issue in merge request diff viewer impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to execute arbitrary JavaScript in the context of another user’s browser session due to improper sanitization of path components in the merge request diff viewer.

Impacted Versions: GitLab CE/EE: all versions from 13.11 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1

CVSS 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-92470 - Missing Authorization issue in Duo AI job troubleshooting feature impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to access sensitive CI/CD variable values from debug-mode job traces through the Duo AI troubleshooting feature due to missing authorization checks.

Impacted Versions: GitLab EE: all versions from 18.7 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1

CVSS 7.7 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N)

This vulnerability has been discovered internally by GitLab team member Daniel Prause

CVE-2026-92874 - Incorrect Authorization issue in MCP API scope enforcement impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with an MCP-scoped token to perform actions beyond the intended scope of that token due to improper authorization checks.

Impacted Versions: GitLab CE/EE: all versions from 18.3 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1

CVSS 5.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N)

This vulnerability has been discovered internally by GitLab team member Amr Taha

CVE-2026-92530 - Use of Less Trusted Source issue in Direct Transfer import user mapping impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to spoof merge request authorship and attribute content to arbitrary existing users on the target instance due to improper reliance on ephemeral cache state during Direct Transfer imports.

Impacted Versions: GitLab CE/EE: all versions from 19.1 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1

CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N)

Thanks ahacker1 for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-8937 - Missing Authorization issue in Epic Issues REST API impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user to read private child issue contents, including titles and descriptions, from projects they had no access to, due to missing authorization checks on linked work items within visible epics.

Impacted Versions: GitLab CE/EE: all versions from 19.0 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1

CVSS 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-92529 - Incorrect Authorization issue in Duo Workflow Service token governance enforcement impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with developer-role permissions to bypass admin-configured AI tool governance controls for workflows in namespaces they do not control due to improper authorization checks.

Impacted Versions: GitLab EE: all versions from 19.1 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1

CVSS 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 Rahul Barnwal

CVE-2026-10518 - Improper Access Control issue in GraphQL memberRoles dependentSecurityPolicies resolver impacts GitLab EE

GitLab has remediated an issue that under certain conditions could have allowed an authenticated user with guest-level permissions to read private security policy content they were not authorized to access due to improper authorization enforcement.

Impacted Versions: GitLab EE: all versions from 17.9 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1

CVSS 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-4523 - Missing Authorization issue in GraphQL CI job trace API impacts GitLab CE/EE

GitLab has remediated an issue that under certain conditions could have allowed an unauthenticated user to read CI/CD job trace contents containing sensitive variable values due to improper authorization enforcement in the GraphQL API.

Impacted Versions: GitLab CE/EE: all versions from 15.11 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1

CVSS 3.7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N)

Thanks scyoon for reporting this vulnerability through our HackerOne bug bounty program

CVE-2026-92628 - Race Condition issue in MCP gitlab_search tool impacts GitLab CE/EE

GitLab has remediated an issue that under a race condition, the MCP search tool’s shared state handling could have caused search results to be returned under an incorrect user context.

Impacted Versions: GitLab CE/EE: all versions from 18.6 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1

CVSS 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 Chris Bonk

Bug fixes

19.4.1

• Backport 19.4 release notes
• Backport of ‘Resume mid-delta on the package metadata label path’ into 19-4-stable-ee
• Backport Add 19.4 release note: Improved table pasting in rich text editor
• Backport Add 19.4 release note: organization security dashboards
• [19.4] Bump gitlab-omnibus-builder version to 5.68.0

19.3.3

• Backport of Adjust docs following patches for "require a commit SHA for merge requests API"
• Backport of ‘Fix backfill migration overlap on empty CI partitions’ to 19-3-stable-ee
• Backport of Fix infinite loop parsing errored SARIF security reports (19.3)
• Bump PostgreSQL to version 17.11 (19-3-stable)
• Bump Consul to version 1.22.7 (19-3-stable)
• Merge branch ‘sdg-fips-staging-upload-internal-release’ into 19.3
• Backport !9672 to 19-3-stable: selinux: add sshd_session_t and sshd_auth_t rules for RHEL 10 / OpenSSH 9.8+
• Backport !9744 to 19-3-stable: Allow sshd fast SSH key lookup under SELinux
• Treat Patroni streaming state as a running node (backport to 19-3-stable)

19.2.7

• ‘Stop resetting mcp_server_enabled when Duo settings change’ to 19-2-stable-ee
• Restore Slack notifications documentation page (19.2 backport)
• Backport of ‘Fall back across resolved IPs in Gitlab::HTTP (Dependency Proxy 599)’
• Backport of ‘Fix backfill migration overlap on empty CI partitions’ to 19-2-stable-ee
• Backport of ‘Resolve orphan artifact lookups in one query per batch’
• Backport of ‘Update GitLab Elasticsearch Indexer to 5.14.14’ to 19.2
• Backport of ‘Specify low urgency of getPipelineDetails query’ to 19.2
• Backport ‘Drop system failure assertion in secrets specs’ to 19-2-stable-ee
• Backport of ‘Stop dependency proxy requests counting against the web rate limit’
• Backport of ‘Add application setting to block JWT for reclaimed project paths’
• Backport of ‘Resume mid-delta on the package metadata label path’ into 19-2-stable-ee
• Bump PostgreSQL to version 17.11 (19-2-stable)
• Bump Consul to version 1.22.7 (19-2-stable)
• Merge branch ‘sdg-fips-staging-upload-internal-release’ into 19.2
• Backport !9672 to 19-2-stable: selinux: add sshd_session_t and sshd_auth_t rules for RHEL 10 / OpenSSH 9.8+
• Backport !9744 to 19-2-stable: Allow sshd fast SSH key lookup under SELinux
• Treat Patroni streaming state as a running node (backport to 19-2-stable)

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.3.3
• 19.2.7

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.

Original source

On September 17, 2026, GitLab 19.4 was released with the following features.

We are excited to recognize Jimmy, a Level 4 contributor, as this month’s Notable Contributor!

Jimmy contributed across the GitLab codebase, client-go, and the Terraform provider to ensure that tokens, service accounts, and push mirrors can be managed end to end through infrastructure as code.

Primary features

Governance for GitLab MCP server tools

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

Previously, you could only apply AI agent tool governance rules to internal GitLab Duo Agent Platform tools. Tools available to both GitLab Duo Agent Platform and third-party agents through the GitLab MCP server followed fixed rules that could not be changed.

You can now govern GitLab MCP server tools from the same place as internal GitLab Duo Agent Platform tools. They appear alongside internal tools in your group and project GitLab Duo settings, where you can set a mode for each tool:

• Read-only tools default to Always Allow, so routine lookups run without interrupting your team.
• Write and delete tools default to Always Ask, giving reviewers a checkpoint before an agent changes anything.

Restrict access to MCP servers (beta)

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

You can now restrict access to MCP (Model Context Protocol) servers by allowing or denying access to:

• An entire external MCP server.
• Individual tools on an MCP server.

This feature gives you assurance that AI agents within Duo Agent Platform are operating within governed boundaries and can only access MCP tools that are within their scope to perform their activities, sessions, and tasks.

These controls apply consistently wherever AI agents run, including:

• Agentic Chat.
• Flows.
• IDE and CLI environments.

This feature is currently in beta and we welcome your feedback in issue #628378.

Vulnerability Context Flow

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Use the Vulnerability Context Flow to produce context to triage vulnerabilities more efficiently and intelligently.

The flow produces context in the following three categories:

• Authentication: Yes or No. Indicates whether the vulnerable code requires authentication to exploit.
• Authorization: Elevated or Standard. Indicates whether exploiting the component requires elevated privileges.
• Sensitive data: Yes or No. Indicates whether the vulnerable code handles sensitive data, such as personal information, credentials, tokens, payment data, or health data.

Advanced SAST includes Kotlin, Dart, and Scala language support

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Advanced SAST now scans Kotlin, Dart, and Scala codebases with the same deep taint analysis that covers Java, Python, and other supported languages, all delivered through the Software Factory architecture with per-language front-ends and framework-aware rule gating.

Kotlin detection targets Android APIs for SQL injection, unsafe WebView usage, OS command injection, hardcoded credentials, and weak cryptography.

Dart detection includes a Flutter and Dio framework detector covering SSRF, path traversal, command injection, and cleartext HTTP.

Scala detection covers Play, Slick, and Akka frameworks for SQL injection, SSRF, open redirect, path traversal, command injection, and XSS.

All three additions are verified using deliberately vulnerable real-code repositories, with findings reported as code flows from source to sink.

SPDX license expression support in dependency and license scanning

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

GitLab license data now carries SPDX license expressions, including compound declarations such as MIT OR Apache-2.0 or GPL-2.0-only WITH Classpath-exception-2.0.

Previously these were reported as unknown in the dependency list and were invisible to license approval policies.

Composite licenses now appear in the dependency list with their operator (AND, OR, WITH), and license approval policies can allow or deny them the same way they handle single-license dependencies.

Expressions declared in a CycloneDX SBOM have been supported since GitLab 19.3. This release adds them to the license data GitLab synchronizes.

Offline instances receive expressions only after downloading the v3 license data.

Agentic Core

/goal command in GitLab Duo CLI

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

GitLab Duo CLI now includes a /goal slash command that delegates open-ended objectives to a governed, goal-driven flow that runs locally.

You describe a goal and GitLab Duo handles implementation and verification, using an independent judge to decide when you have achieved your goal or reached the iteration limit. You stay in control the whole time: pause, update the goal, or redirect the agent at any time.

The /goal slash command requires GitLab 19.3 and later, and GitLab Duo CLI 9.17.0 and later.

To get started, run /goal <task>.

For example:

/goal Fix the failing tests in spec/models/user_spec.rb

GitLab Duo Slack integration (Experimental)

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

You can now invoke GitLab Duo agent flows directly from Slack, without switching to the GitLab UI.

With the GitLab Duo Slack integration, you can mention GitLab with @GitLab in any Slack channel or thread. Mention GitLab to trigger agent flows, get answers from your codebase, and create GitLab issues from conversations. GitLab Duo streams its progress back into the Slack thread in real time, and includes thumbs-up and thumbs-down feedback buttons so you can rate responses without leaving Slack.

This integration is available as an experiment. To share your feedback, add a comment to issue 624364.

GitLab flow builder for custom flows (Beta)

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Build custom flows for your GitLab projects with the GitLab flow builder, a new visual editor for AI-native workflows in the GitLab for VS Code extension.

Compose a flow visually from components (Agent, Custom tool, and AI task), or edit the underlying YAML directly.

To start, open your flow’s YAML file in VS Code and select Open GitLab Flow Builder.

Test your flow with the Run button, which opens an execution console.

When your flow is ready, select Publish to publish it to the AI Catalog.

The flow builder is available as a beta feature in GitLab for VS Code 6.87.0 and later. To get started, enable the gitlab.featureFlags.flowBuilder setting in VS Code.

MCP server CI/CD tools

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

New CI/CD tools let agents trigger, inspect, and control CI/CD from any MCP client:

• save_pipeline runs, retries, or cancels a pipeline without switching tools.
• get_job returns job metadata together with the job trace, so an agent can read the log of a failed build and diagnose the problem on its own.

Previously, agents had no way to trigger or inspect pipelines through MCP.

MCP server merge request tools

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Merge request tools let agents run the full merge request loop through the GitLab MCP server:

• save_merge_request opens and updates an MR.
• get_merge_request inspects an MR in depth, with new diffs, conflicts, and approvals facets.
• save_merge_request_review leaves line-level review comments, with batched diff comments and a summary in a single call.
• accept_merge_request merges an MR once checks pass, and can also approve or unapprove it.

MCP server project and user tools

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

New project and user tools give agents the context they need to target work correctly through the GitLab MCP server:

• list_projects finds and reads project details.
• get_user looks up user details for assignment and mentions.

Previously, agents had no way to discover project or user information through the GitLab MCP server.

MCP server repository tools

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

New repository tools let agents browse a project’s structure, read its commit history, and propose changes through the GitLab MCP server:

• list_repository_tree explores the file tree.
• list_tags enumerates refs.
• list_releases inspects published releases.
• get_commit retrieves a commit’s metadata, diff, or notes.
• list_commits pages through a branch’s history.
• add_commit commits one or more file actions in a single call, optionally to a new branch from a specific starting ref or source project.
• fork_repository forks a project, so an agent can go from exploring an upstream repository to proposing changes without leaving its client.

MCP server semantic search tool

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

semantic_code_search is now semantic_search. The tool finds code by meaning rather than by exact symbol or filename, which is unchanged from earlier releases. The rename adds a scope parameter so that additional indexed content types can fold into the same tool in future releases. Today scope accepts code only.

Thank you to arun kumar for this contribution!

MCP server work item tools

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

The GitLab MCP server now exposes work item tools, so agents and MCP clients can search, read, create, and update issues, epics, tasks, incidents, objectives, and key results.

Use get_work_item to read a single item in depth, list_work_items to search across a group or project, and save_work_item to create or update any work item type.

Because issues and epics are work item types, get_work_item and save_work_item cover what get_issue and create_issue do today.

save_note lets an agent comment on a work item or merge request and reply inside an existing discussion thread. The introduction of this tool renames existing create_merge_request_note and create_workitem_note.

Merge request created event trigger

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, the Merge request trigger event type only supported the Approved, Marked ready, and Merge conflict actions. You had no way to run a flow or external agent the moment someone opened a merge request without using a tool outside GitLab.

You can now select Created as a trigger action. When someone opens a merge request in draft or ready state, and GitLab generates the diff, your flow or external agent runs. Use this for a first-pass review, or to add context from related issues.

To configure this trigger, go to AI > Triggers in your project, or select it when you enable a flow.

Redesigned session details panel for the GitLab Duo Agent Platform

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Finding the details that matter about an agent session used to mean hunting through a cluttered panel.

Now, the session details panel surfaces what you need at a glance: status, timestamps, and the triggering user appear in an overview bar, while the right rail organizes identity, execution, and supplemental details into clearly labeled groups.

A new Linked items section separates what started the session from what it produced, including merge requests, work items, jobs, and comments. In the GitLab Duo side panel, session details now live in a collapsible bar pinned to the bottom, so they stay accessible without getting in your way.

Model selection for the Developer Flow

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

The GitLab Duo Agent Platform now supports independent model selection for the Developer Flow.

As an administrator, you can select a specific AI model for the Developer Flow separately from other GitLab Duo Agent Platform features, giving teams greater control over model selection.

Support for GLM 5.3, Kimi K3, and MiniMax M3 in GitLab Duo Agent Platform

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

The GitLab Duo Agent Platform now supports three open-weight models: GLM 5.3, Kimi K3, and MiniMax M3.

In GitLab Duo Agentic Chat, you can select any of these models for your own conversations. Users with the Owner role for a group and administrators can also set them as the default for Agentic Chat and for other agents, flows, and features.

Turn flow triggers off without deletion

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, the only way to stop a trigger from automatically starting a flow was to delete it entirely.

Deleting a trigger meant losing any complex filter configuration you had set up.

Now you can turn a flow trigger off and retain its configuration.

Use the new toggle to turn it back on at any time.

To manage triggers, go to AI > Triggers.

Unified DevOps and Security

Automated Triage and Remediation profile (GraphQL API)

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, you turned on SAST false positive detection, GitLab Duo Vulnerability Resolution, secret detection false positive detection, and dependency scanning auto-remediation for each project individually. Now you can apply an Automated Triage and Remediation profile to a group or project, setting severities and run modes in one action. Start with a preset, or configure each flow yourself:

• Conservative: on demand, high severity.
• Standard: automatic, medium severity and above.
• Proactive: automatic, every severity.

Profiles are available only with the GraphQL API, and require GitLab Duo Agent Platform with foundational flows turned on for the top-level group. Most flows consume GitLab Credits.

See who locked a file or directory

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

When a file is locked, you now see who locked it and what your options are, without leaving the blob viewer.

Previously, only a Locked label appeared, with no way to tell who locked the file or whether you could unlock it yourself. Now, a popover next to the label shows who locked it. If you have permission to unlock the file, the popover includes an unlock action. If you don’t, it explains why. For locked directories, the popover links you directly to the specific file that’s blocking your changes.

Vulnerability Due Date API

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Security teams can use the bulkSetVulnerabilityFindingsDueDates GraphQL mutation to assign, update, or remove due dates for vulnerability findings in bulk. Each request supports up to 1,000 finding UUIDs and returns counts for assigned, removed, and skipped updates, along with structured errors. Teams can use this information to connect vulnerability remediation timelines with existing service-level agreement (SLA) and workflow automation.

Aggregated scanner coverage in security inventory

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

You can now view scanner coverage for an entire group hierarchy from one page. In previous versions of GitLab, the Security Inventory showed coverage per subgroup, but no total for the entire group. A coverage widget now aggregates scanner coverage across every project in the group and its subgroups, and shows the percentage and number of projects where each scanner is enabled, not enabled, failing, or stale. To focus on one scanner, such as SAST or Dependency Scanning, use the scanner dropdown list. Then select a status to filter the project list, and turn on scanners for the projects that aren’t covered.

The Security Inventory also now lets you control which columns are shown. To show or hide the Vulnerabilities, Tool coverage, and Security attributes columns, select Display.

Automatic revocation for routable personal access tokens

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

When secret detection finds a leaked GitLab personal access token in a public project, automatic response revokes it. In GitLab versions earlier than 19.4, revocation used only one detection rule and revoked only the legacy token format.

Tokens created on GitLab 18.3 and later use the routable or versioned routable format. GitLab detected and reported these tokens without revoking them.

In GitLab 19.4 and later, revocation recognizes all three GitLab personal access token detection rules:

• gitlab_personal_access_token
• gitlab_personal_access_token_routable
• gitlab_personal_access_token_routable_versioned

Revocation also covers findings from GitLab Secret Scanning for Source Code and the Gitleaks-based analyzer.

You do not need to change any configuration.

Instances with automatic response enabled get this wider coverage immediately.

GitLab Runner 19.4

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

We’re also releasing GitLab Runner 19.4 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

• Fastzip is now the default archiver for caches and artifacts
• Add runner and system_id labels to gitlab_runner_job_router_get_job_duration_seconds
• Add a dedicated SLI, SLO, and alerting integration for the Job Router
• Add suspend and resume support for the Kubernetes executor
• Emit the environment key on job-complete PUT request
• Option to suppress the cache upload and download URL in job logs
• Add services_cap_add and services_cap_drop options to the Docker executor configuration

Bug Fixes

• Job router 409 responses disable runner managers for an hour
• The logrotate usage writer can panic the runner by mutating shared runner labels
• Windows service console restore failure force-kills a job that is stopping gracefully
• Unbounded cardinality for the job_id and runner_controller_id attributes in a histogram
• Config validation warns got null for nil-able fields that have a TOML tag but no JSON tag
• Intermittent silent failure in get_sources caused by SIGPIPE in the Git version check
• Spurious Request bottleneck warning when FF_USE_ADAPTIVE_REQUEST_CONCURRENCY is enabled
• Secret-resolution failures for AWS, GCP, Azure, and GitLab Secrets Manager are now classified by cause
• Kubernetes pause pods fail to start when the runner short ID begins with -
• Canceling a job always results in a process kill when running as a Windows service

The list of all changes is in the GitLab Runner CHANGELOG.

Improved table pasting in rich text editor

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Previously, pasting a copied table into a table cell always merged the copied cells into the existing table, which made it difficult to create a nested table.

Now you can choose how a pasted table behaves:

• Select Paste into cell to insert the copied table as a nested table inside the cell.
• Select Paste and merge into table to distribute the copied cells across the existing table, which remains the default behavior.

You can also use a keyboard shortcut to paste a table into a cell as a nested table: Command+Option+V on macOS, or Control+Alt+V on Windows and Linux.

Standard paste with Control+V or Command+V works as it did before.

Malicious package detection in Dependency Scanning (Beta)

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, Dependency Scanning only surfaced packages with known CVEs. Malicious packages, those crafted to harm through typosquatting, compromised maintainer accounts, or embedded malware, produced no findings.

GitLab 19.4 introduces malicious package detection in beta. Dependency Scanning now checks your dependencies against GitLab malware advisories, so threats can surface before they are widely known. Findings appear in your Dependency List and Vulnerability Report with a red Malware badge, always Critical severity, identified by a GLAM- ID, not a CVE.

You can also block malicious packages before they merge, using the malware rule in merge request approval policies.

You don’t need any additional setup. Coverage applies to the supported package types:

• npm, PyPI, Maven, Go, NuGet, Cargo, and RubyGems.

The same advisories power continuous vulnerability scanning, and offline instances download them manually.

Share feedback on issue 606036.

Organization security dashboards (Beta)

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

Security dashboards are now available at the organization level.

Users can see the following data across all top-level groups in an organization:

• Vulnerability severity panels
• Vulnerabilities over time
• Top 10 CWEs
• Risk score
• Vulnerabilities by age

Vulnerability tools added to the GitLab MCP server

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In GitLab 19.4, the GitLab MCP server provides the following new tools for vulnerability management:

• list_vulnerabilities, which lists security vulnerabilities in a GitLab project with optional filtering by severity and report type, with cursor pagination.
• get_vulnerability, which fetches full details for a single vulnerability by numeric ID, converting it to the gid://gitlab/Vulnerability/<id> global ID format.
• save_vulnerability, which covers five write operations on GitLab vulnerabilities in a single consolidated tool:
  • Mark a vulnerability as dismissed, with optional comment and dismissal reason.
  • Mark a vulnerability as confirmed.
  • Revert a vulnerability’s state back to detected.
  • Override the severity with a required comment.
  • Create a new issue linked to the vulnerability.

These new vulnerability management tools allow AI agents to run vulnerability triage and remediation actions through the GitLab MCP server.

Scale and Deployments

Early warnings for GitLab Flex spend caps

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

GitLab 19.3 introduced email notifications for reservation thresholds and for the moment a capped capability is cut off. The spend cap itself had no early warning, so the first email about a cap arrived when usage had already stopped.

GitLab now emails billing account managers when a capability’s on-demand usage reaches 50% or 80% of its monthly spend cap, naming the capability and the cap in credits. Only the highest threshold crossed is sent, at most once per capability per billing period. Caps of less than $10 are skipped, so a small cap does not generate noise.

Geo SSH proxying enabled by default

Tier: Premium, Ultimate
Offering: GitLab Self-Managed
Links: Documentation · Related Issue

The following feature flags are enabled by default in GitLab 19.4:

• geo_proxy_fetch_ssh_to_primary
• geo_proxy_push_ssh_to_primary

Geo SSH proxying provides a more reliable path for SSH fetches and pushes to a Geo secondary site when the operation is proxied to the primary site. It also resolves long-standing bugs where proxied operations failed, such as pushes with push options and fetches from large repositories.

Action required for Cloud Native GitLab deployments

Cloud Native GitLab deployments using the bundled NGINX Ingress must either:

• upgrade to use the Gateway API with Envoy Gateway before this rollout, or
• disable both feature flags after the rollout.

Otherwise, SSH fetches and pushes through Geo secondaries may hang or time out.

See the Geo troubleshooting documentation for SSH proxying for more information.

Included credits are used before evaluation credits

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

When a subscription had temporary evaluation credits, all usage drew from that shared pool first. Every user’s included monthly credits sat idle until the evaluation pool ran out, and then reset at the end of the month.

GitLab now consumes each user’s included credits first, and draws from the shared pool of temporary evaluation credits only after a user has used their included amount. The Monthly Commitment Pool, One-Time Charge credits, and On-Demand credits are consumed in the same order as before, so your bill is unaffected.

Per-event detail in the credit usage export

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

The credit usage export gave you one row per day, which told you how much a subscription spent but not what it spent on. Attributing credits to a team, a project, or a single automation meant guesswork.

The export now returns a ZIP file with two CSV files: the daily summary you already had, and a per-event file with one row for each billable event. Each row includes the product, flow type, session, user, namespace, project, credits used, and token counts. Exports run in the background, and GitLab emails you a download link when the file is ready.

Set credit caps without the GraphQL API

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed
Links: Documentation · Related Issue

Credit caps limit how many GitLab Credits each user can consume, but until now you could only configure them through the GraphQL API. Setting a different cap for a handful of users meant writing mutations by hand.

The new Credit caps page lets you set the flat cap that applies to every user by default, and add per-user overrides for individual users through a searchable picker.

This page is available in GitLab Credits for group Owners on GitLab.com and administrators on GitLab Self-Managed.

The GraphQL mutations still work if you prefer to script cap changes.

Co-created contributions

Diagnose LDAP group sync failures

Tier: Premium, Ultimate
Offering: GitLab Self-Managed
Links: Documentation · Related Issue

When an LDAP group sync fails, the reason now reaches you. The failure is recorded against the group, the members that caused it are named (up to five), and a danger alert appears on the group members page, so a sync blocked by an email-domain restriction is diagnosable from the UI. A new group_filter setting lets you narrow which LDAP entries count as groups. The audit log also distinguishes causes that previously shared one entry: LDAP group links created and removed, and users blocked by LDAP sync, each now get their own audit event type.

Thank you to Sergey Pechenko for these contributions (MR 1 MR 2 MR 3 MR 4)!

Merge request widget is now more specific

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

While GitLab checks a merge request, the widget now tells you. Merge conflicts must be resolved becomes Checking for merge conflicts until the check finishes. When a rebase is refused, you see the specific reason, such as Source branch is protected from force push, instead of a generic retry prompt. You can act on the current state of the merge request.

The sticky title bar that stays visible while scrolling a merge request now also updates immediately when you mark it draft or ready, instead of requiring a page refresh.

Thank you to the following users for these contributions!

• Amartya Mishra (MR 1 MR 2)
• Gerardo Navarro (MR)
• Mahaveer A (MR)

GitLab MCP server tools from the community

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Community contributors added new tools for the GitLab MCP server. Agents can now use get_project and list_project_members to read project metadata and members, list_branches to list a repository’s branches, and list_merge_requests to list merge requests across a whole group. get_duo_session fetches a GitLab Duo session so you can see what an earlier run did.

These tools ship alongside the other new GitLab MCP server tools in 19.4 and run under the same tool governance, so an agent using them follows the rules your team already set.

Thank you to the following users for these contributions!

• Dhairya Majmudar (MR 1 MR 2)
• Giannis Kepas (MR 1 MR 2)
• Mahaveer A (MR)

Preview a new file before commit

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

The new file page now has Write and Preview tabs, the same pair the edit page has had for years, so you can see how a Markdown or AsciiDoc file renders before its first commit exists.

Preview keeps up with your edits: rename a file from .txt to .md mid-edit and the preview switches renderer; rename it away from Markdown and the live preview stops. Snippets also gained Markdown live preview, available from the editor’s right-click menu.

Thank you to skkzsh for this contribution!

Additional feature enhancements

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Other improvements in this release include:

• Fetch a specific report artifact from the API, restricted to downloadable types and gated by a per-artifact authorization check. For example, use GET /projects/:id/jobs/:job_id/artifacts?file_type=junit for a JUnit file.
• Administrators can let clients choose between a direct 302 redirect and a proxied transfer for job artifact and package downloads.
• The pipeline editor now validates CI/CD keywords the backend already supported.
• An email with an empty subject line now opens a Service Desk ticket instead of bouncing.
• Raise dependency resolution limits yourself with two new timeout inputs on the Dependency-Scanning.v2 template.
• Administrators can set achievements to appear on profiles without each person accepting an emailed link.

Thank you to the following users for these contributions!

• Andreas Kunze (MR)
• André Düwel (MR)
• Paweł Farys (MR)
• Praveen Arimbrathodiyil (MR)
• Niklas van Schrick (MR)
• BoxBoxJason (MR)

Other additions to the interface

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Other additions to the interface in this release include:

• Filtering the issue list by created, closed, due, and updated date is now generally available for everyone.
• Starting a merge request from a cherry-picked commit now has a checkbox to copy the source merge request’s description instead of the project template.
• /internal_note marks a comment internal as you create it, so internal notes can live inside comment templates and saved replies.
• /type Epic promotes an issue to an epic, the same as /promote_to Epic.
• Links in Mermaid flowcharts now open, and diagrams render without clipping in Chrome on iOS.

Thank you to the following users for these contributions!

• Radek Antoniuk (MR)
• Viktor Chekryzhov (MR)
• Priyansh Garg (MR)
• Aryann Dwivedi (MR)
• skkzsh (MR)
• Jordan Labrosse (MR)

Original source

Update: On September 23, 2026, we backported fixes for CVE-2026-85706 and CVE-2026-87719 to versions 19.0.9 and 18.11.12 of GitLab Community Edition (CE) and Enterprise Edition (EE). Self-managed GitLab administrators running older versions of GitLab CE and EE can now upgrade to these versions to apply these security fixes.

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

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

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 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2

CVSS 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.

Detecting CVE-2026-85706 Exploitation Attempts

CVE-2026-85706 has been added to CISA’s Known Exploited Vulnerabilities catalog. GitLab-managed infrastructure, including GitLab.com and GitLab Dedicated, remains patched. GitLab security has released three threat detections to support customers with self-managed instances:

• GitLab LFI attempt reading gitlab.yml
• GitLab LFI via metadata.path parameter
• GitLab LFI file path attempt

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 18.11.12, 19.0 before 19.0.9, 19.1 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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-7514 - Missing Authorization issue in Generic Package Registry impacts GitLab CE/EE

GitLab has remediated an issue that an authenticated user with developer-role permissions could substitute package file content and hide packages from their owners due to improper authorization checks in the Generic Package Registry.

Impacted Versions: GitLab CE/EE: all versions from 13.9 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2

CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N)

Thanks toofikz for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-8030 - Improper Input Validation issue in Namespace Transfer impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user to prevent another user from modifying their group settings due to improper validation of group URL slugs during namespace transfers.

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.2

CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L)

Thanks mateuszek for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-16794 - Missing Authorization issue in Compliance Framework management impacts GitLab EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user with the Security Manager role to execute arbitrary CI/CD jobs and access protected variables within group projects due to improper authorization controls on compliance framework management.

Impacted Versions: GitLab EE: all versions from 18.11 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2

CVSS 4.3 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N)

Thanks manual_mint for reporting this vulnerability through our HackerOne bug bounty program.

CVE-2026-3855 - Improper Input Validation issue in Terraform State API impacts GitLab CE/EE

GitLab has remediated an issue that, under certain conditions, could have allowed an authenticated user with project-level permissions to access restricted file contents on the server or cause denial of service due to improper validation of parameters in the Terraform state upload functionality.

Impacted Versions: GitLab CE/EE: all versions from 18.2.7 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2

CVSS 3.1 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N)

Thanks ahacker1 for reporting this vulnerability through our HackerOne bug bounty program.

Bug fixes

19.3.2

• 19.3 Backport: Update Ruby version from 3.3.11 to 3.3.12
• Update go to version 1.26.7
• Revert “Merge branch ‘replace_ftp_gnu_org_with_mirror’ into 19.3
• Add whole-diff hash option to GetPatchID
• Backport of ‘Skip Lockable reset_failed_attempts! on read-only replicas’
• Backport of “Show “No available solution” message for CS when solution is empty”
• Backport of ‘Reuse HTTP connections and add timeouts in Gitlab::HttpIO’ (19.3)
• Backport of ‘Cache the previous chunk in Gitlab::HttpIO’ (19.3)
• Backport of ‘Fix broken gcloud auth plugin package name in qa/Dockerfile’
• Backport of Set SHA requirement to false on group creation if ancestor is not locked
• Backport of “Stop logging GraphQL type conflict deprecation warnings”
• Bump websocket-driver from 0.8.0 to 0.8.2 (backport to 19-3-stable-ee)
• Restore Slack notifications documentation page (19.3 backport)
• Backport of Geo: Missing index on ci_job_artifact_states causes slow re-verification UPDATE queries
• Quarantine flaky agentic chat custom-agent spec [19.3]
• Backport of ‘Geo: Support SSH cert gl_id formats in proxied Git requests’
• Backport of ‘Fix empty partition range crashing pipeline lookups (CI outage)’ to 19-3
• Backport of ‘Restore Bitbucket Cloud API-token imports without OAuth provider’
• Backport ‘Stop resetting mcp_server_enabled when Duo settings change’ to 19-3-stable-ee
• Bump concurrent-ruby to version 1.3.8 (19-3-stable)
• Bump alertmanager to v0.34.0 (19-3-stable)
• Bump NGINX to 1.31.4
• Update GO to 1.26.7 on 19-3-stable
• Update dependency redis/redis to v7.2.16 (19-3-stable)

19.2.6

• Update go to version 1.26.7
• Revert “Merge branch ‘replace_ftp_gnu_org_with_mirror’ into 19.2
• Add whole-diff hash option to GetPatchID
• Backport of ‘Fix quadratic line reading in CI trace reverse scan’ (19.2)
• Backport of ‘Optimize remote CI artifact parsing and size validation’ (19.2)
• Backport of ‘Skip Lockable reset_failed_attempts! on read-only replicas’
• Backport of ‘Reuse HTTP connections and add timeouts in Gitlab::HttpIO’ (19.2)
• Backport of ‘Cache the previous chunk in Gitlab::HttpIO’ (19.2)
• Backport of ‘Fix broken gcloud auth plugin package name in qa/Dockerfile’
• Backport of “Admin setting for cyclonedx report max size”
• Backport of Set SHA requirement to false on group creation if ancestor is not locked
• Bump websocket-driver from 0.8.0 to 0.8.2 (backport to 19-2-stable-ee)
• Quarantine flaky agentic chat custom-agent spec [19.2]
• Backport of ‘Fix empty partition range crashing pipeline lookups (CI outage)’ to 19-2
• Increase staging_upload_template and production_release_template timeout from 35m to 60m
• Bump concurrent-ruby to version 1.3.8 (19-2-stable)
• Bump alertmanager to v0.34.0 (19-2-stable)
• Bump NGINX to 1.31.4
• update go 1.26.7 on 19-2-stable
• Update dependency redis/redis to v7.2.16 (19-2-stable)

19.1.8

• Update go to 1.25.14
• Revert “Merge branch ‘replace_ftp_gnu_org_with_mirror’ into 19.1
• Backport !8857 to 19-1: Fall back to full backup when previous step is non-existent
• Add whole-diff hash option to GetPatchID
• Backport of ‘Skip Lockable reset_failed_attempts! on read-only replicas’
• Backport of ‘Fix broken gcloud auth plugin package name in qa/Dockerfile’
• Quarantine flaky agentic chat custom-agent spec [19.1]
• Backport of ‘Fix empty partition range crashing pipeline lookups (CI outage)’ to 19-1
• Increase staging_upload_template and production_release_template timeout from 35m to 60m
• Bump concurrent-ruby to version 1.3.8 (19-1-stable)
• Bump alertmanager to v0.34.0 (19-1-stable)
• Bump NGINX to 1.31.4
• Update go to 1.25.14 on 19-1-stable
• Update dependency redis/redis to v7.2.16 (19-1-stable)

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.3.2

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.

Original source

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

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

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.1

CVSS 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.1

CVSS 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.1

CVSS 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.1

CVSS 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.1

CVSS 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.1

CVSS 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.1

CVSS 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.

Original source

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.

GitLab Secrets Manager now available on GitLab.com

Tier: Premium, Ultimate
Offering: GitLab.com
Add-ons: GitLab Secrets Manager
Links: Documentation · Related Issue

Credential leaks often start the same way: a developer needs a secret, has no good place to put it, and drops it into an over-scoped CI/CD variable or a committed config file. GitLab Secrets Manager, now in Limited Availability on GitLab.com, makes credentials more secure and keeps them in the same platform that runs your pipelines.

Each secret is scoped to the job that needs it, based on environment, branch, and branch protection, so a compromised credential can’t reach more than it’s authorized to. Secrets Manager uses your existing group and project permissions, so there’s no separate access model to maintain. Every create, update, and read is logged to your audit trail, so a leak investigation doesn’t mean stitching together logs from multiple systems.

GitLab Secrets Manager is an add-on billed through GitLab Credits. Start a free 30-day trial to explore all features. Learn more about billing and trials in the billing documentation.

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 <plugin>@gitlab-duo-plugins or duo plugin install <plugin>@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 Agentic Chat UI in VS Code and JetBrains IDEs (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 and the GitLab Duo plugin for JetBrains IDEs 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 6.88.1 and later
• GitLab Duo plugin for JetBrains IDEs 3.45.2 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.

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.

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. Now GitLab reads and stores the expression field from CycloneDX license entries, including complex expressions like MIT AND Apache-2.0 and custom license references using the LicenseRef-[NAME] syntax.

SPDX expression support is especially useful for organizations that generate their own SBOMs and have components with complex or custom license expressions, giving you an accurate view of your license exposure without requiring GitLab-generated scans.

For more information, see Bring your own CycloneDX SBOM.

Audit events for secret push protection fail-open scenarios

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In earlier versions of GitLab, when secret push protection couldn’t complete a scan and allowed a push through unscanned, GitLab provided no customer-visible audit trail. Security and compliance teams had no way to monitor when secret push protection silently allowed a push to their repositories.

GitLab 19.3 and later generates audit events for all fail-open scenarios, including ruleset errors, exceeded file and line limits, scan timeouts, and unexpected errors. Teams can now forward these events to external monitoring and alerting tools to maintain visibility into their security posture.

Dependency scanning support for Bun

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

In previous versions of GitLab, projects using the Bun JavaScript runtime and package manager had no dependency scanning coverage. Now, GitLab dependency scanning analyzes Bun projects by parsing bun.lock files (the text-based JSONC format introduced in Bun 1.2).

Because Bun packages are sourced from the npm registry, the GitLab advisory database already covers these dependencies with no additional configuration required.

Teams using Bun as an alternative to npm, yarn, or pnpm can now scan their projects for known vulnerabilities as part of their standard CI/CD pipelines. Eligible findings are also supported by dependency scanning auto-remediation.

Execute SAST false positive and vulnerability resolution flows in bulk

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed
Links: Documentation · Related Issue

In the Vulnerability Report, you can now select multiple vulnerabilities and run SAST Vulnerability Resolution and SAST False Positive Analysis flows on all of them at once.

GitLab Runner 19.3

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

We’re also releasing GitLab Runner 19.3 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

• Document Job Router version compatibility matrix
• Verify Workhorse is in the KAS to Rails request path for Job Router

Bug Fixes

• clear-docker-cache prunes all unused images when IMAGE_FILTER_FLAGS is empty
• Concrete-mode dispatch skips steps where When is unset
• PrintPodWarningEvents doesn’t work
• Custom executor fails when the .git folder is corrupt

The list of all changes is in the GitLab Runner CHANGELOG.

Kubernetes 1.36 support

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

GitLab now fully supports Kubernetes version 1.36. To deploy your applications to Kubernetes and access all features, upgrade your connected clusters to the most recent version.

For more information, see supported Kubernetes versions for GitLab features.

Redesigned vulnerability details page

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

The vulnerability details page has been refreshed with an updated design that makes reviewing and triaging vulnerabilities easier and more efficient.

SAST triage and remediation funnel

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

The Security Dashboard now includes a SAST triage and remediation funnel.

This funnel shows how critical and high SAST vulnerabilities move through triage and remediation over a 30-, 60-, or 90-day window. The funnel traces each stage: detected vulnerabilities, true positives confirmed by SAST false positive detection, vulnerabilities with merge requests created by Agentic SAST Vulnerability Resolution, and vulnerabilities fixed by merged merge requests.

These stages show how much of your workflow AI powers and which stages you can scale further.

Scale and Deployments

PostgreSQL 18.4 option available for fresh installs using the Linux package

Tier: Free, Premium, Ultimate
Offering: GitLab Self-Managed
Links: Documentation · Related Issue

You can now opt-in to using PostgreSQL 18.4 when performing a fresh install using the Linux packages. Upgrades to PostgreSQL 18.4 for existing installations is not yet supported.

For more information, refer to the relevant documentation.

Restricted visibility for custom agents and flows

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

You can now set custom agents and custom flows to Restricted visibility for every group, subgroup, and project in your top-level group.

Previously, you could only set a custom flow or agent to Private (one project only) or Public (visible to everyone on GitLab.com). When you set the visibility to Restricted, the flow or agent is visible to only groups, subgroup, and projects in your top-level group. This ensures that internal logic about your custom agents and flows are not shared outside your company or organization.

Advanced SAST for iOS in beta

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

GitLab Advanced SAST now supports Objective-C and Swift, bringing the same interprocedural taint analysis it delivers for other languages to iOS development. The beta is available for all GitLab Ultimate customers starting in GitLab 19.3.

The beta detects key OWASP Mobile Top 10 vulnerability classes, including insecure data storage, broken cryptography, insecure communication, and authentication and authorization flaws. When a vulnerability begins in one language and reaches a sink in the other, Advanced SAST detects the complete taint path, including paths that cross the Swift and Objective-C language boundary.

To enable, set GITLAB_ADVANCED_SAST_ENABLED: 'true' in your pipeline. If your project contains Objective-C or Swift files, the gitlab-advanced-sast-ext job runs automatically.

For full setup instructions, see the Advanced SAST documentation.

Share feedback in the beta feedback issue.

Email notifications for GitLab Flex usage

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, you had no warning when your Flex usage approached a limit. GitLab now sends billing account managers an email notification when a product reaches 50%, 80%, or 100% of its monthly reservation, and when a capped product reaches its spend cap and is cut off for the rest of the billing period. Each threshold triggers at most one email per product per billing period, so you can act on overage early without getting repeat emails for the same threshold.

GitLab Credits usage caps are generally available

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

On-demand usage can run up overage charges you didn’t plan for. Usage caps for GitLab Credits are now generally available: set a subscription-level cap on on-demand credits in Customers Portal, and set a default per-user cap or per-user overrides with the GraphQL API. When consumption reaches a cap, features that consume GitLab Credits, like GitLab Duo Agent Platform, are suspended until the next billing period begins or an administrator adjusts the cap. Usage caps were introduced in GitLab 18.11 behind the budget_caps_graphql_api feature flag. In GitLab 19.3, the feature flag is removed.

Per-capability spend caps for GitLab Flex

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

With GitLab Flex, overage from one capability draws down the same commitment every other capability depends on. You can now set a spend cap for each capability when you adjust your Flex reservation in the Customers Portal: Restricted (no overage past the reservation), Usage cap (a bounded amount of overage), or Unlimited (unlimited overage past the reservation). When a capped capability reaches its cap, its usage stops for the rest of the billing period, and capabilities without a cap keep running.

Co-created contributions

Branch names can carry the name of whoever created the branch

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

You can include the creator in branch name templates with a new %{branch_creator} variable, so a branch created from an issue can identify who created it rather than falling back to a generic name.

Thank you to Radek Antoniuk for this contribution!

LDAP group sync can now manage the Auditor role

Tier: Premium, Ultimate
Offering: GitLab Self-Managed
Links: Documentation · Related Issue

You can now use LDAP group sync for GitLab Self-Managed instances to grant and revoke the Auditor role automatically. A new audit_group setting maps an LDAP group to Auditor, working the same way admin_group already did for administrators, so auditor access follows directory membership instead of being maintained by hand.

Thank you to Sergey Pechenko for this contribution!

More ways to filter and manage through the API

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

Six improvements are now available across the REST and GraphQL APIs:

• Groups queries accept visibilityLevel and includeSubgroups, and can filter for groups scheduled for deletion with aimed_for_deletion.
• The merge requests REST API accepts merged_after and merged_before.
• Achievement award messages can be edited after being granted, rather than only set at award time.
• Administrators can reset SCIM tokens through the admin token API.
• CI_JOB_TOKEN can now fetch repository archives, which unblocks private Composer package downloads that broke when source fallback was deprecated.

Thank you to the following users for these contributions!

• Colin Jacob Boby (MR)
• nagraj raikar (MR 1 MR 2)
• Niklas van Schrick (MR)
• Nicholas Wittstruck (MR)
• Alessandro Lai (MR)

Other additions to the interface

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

Improvements to the interface in this release include:

• You can press Esc to cancel a list item drag in an issue, work item, or epic description, instead of being stuck completing the move.
• Pipeline test report summary columns are now sortable, defaulting to most failures first.
• And archived labels say Archived in their tooltip, so you can tell at a glance why one looks different.

Thank you to the following users for these contributions!

• Radek Antoniuk
• Saurav Kumar
• Nicholas Wittstruck

Two new CI/CD variables: retry count and job tags

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

Your pipeline scripts can now tell whether they are running for the first time. CI_JOB_RETRY_COUNT holds how many times the current job has been retried and is 0 on the first run, so retry-aware logic no longer needs you to track state yourself. Separately, CI_JOB_TAGS exposes the job’s own configured tags, where previously only the runner’s tags were visible through CI_RUNNER_TAGS. Both are available with no configuration.

Thank you to Giannis Kepas and Dwight Blake for these contributions!

Webhooks for merge request reviews and deployment approvals

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

You can use webhooks for merge request reviews and deployment approvals. When you submit a merge request review as Request changes or Reviewed, GitLab fires a merge_request webhook carrying a changes.reviewers entry, so external tools can react to review activity instead of just approvals.

The deployment webhook gains blocked, approved, and rejected statuses with top-level approver and approval fields, letting you follow a deployment through its full approval lifecycle. The blocked status is available in all tiers. The approved and rejected statuses are available in Premium and Ultimate only, and approver.email is redacted.

Thank you to Messias Tayllan (MR) and Anvita Gupta (MR) for these contributions!

Original source

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

Title Severity Code Injection issue via GraphQL directive impacts GitLab CE/EE Critical Cross-Site Request Forgery issue in GraphQL multiplex query handler impacts GitLab CE/EE High

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.4

CVSS 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.4

CVSS 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.

Original source

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

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

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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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)
• Backport of “Trigger dep-bump resolution on merge request pipeline failures” to 19.2
• Backport of ‘Add Orbit settings alias for knowledge_graph’
• Backport !247590 to 19.2: Fix pipeline test report timeout on large pipelines
• Backport of ‘Add traversal_path sbom_component_versions to CH’ to 19.2
• Backport of “Preserve Geo verification retry fields across resyncs”
• Backport !241962 to 19.2: Make Ci::JobDefinition config size limit configurable - Fix failing pipelines when job config over 1 MiB
• Backport of ‘Fix Codex Agent to use gpt-5.3-codex instead of deprecated gpt-5.1-codex’
• Backport of “Fix duplicated content when copying across blob viewer chunks”
• Backport of ‘Geo: Add targeted container repository reverification task’
• [19.2] Remove project_id FKs from two Geo verification state tables
• Backport of ‘Add Siphon ClickHouse cleanup Rake task’
• [19.2] CI: Only set gitlab.com credential helper on gitlab.com
• Revert to jemalloc 5.3.0 (19-2-stable backport)

19.1.4

• Backport of ‘Pre-approve GitLab MCP server read tools in the token claim’
• Backport to 19.1: Release note CI job fix - MR pipelines only
• Backport changes Add rate limit to index integrity worker
• Backport of: Fix DUO_WORKFLOW_DEFINITION env var for custom flows
• Backport !247590 to 19.1: Fix pipeline test report timeout on large pipelines
• Backport of “Preserve Geo verification retry fields across resyncs”
• Backport !241962 to 19.1: Make Ci::JobDefinition config size limit configurable - Fix failing pipelines when job config over 1 MiB
• Backport of ‘Fix 500 when fetching vulnerability notes via REST API’
• 19.1 Backport of ‘Fix 500 when securityReportFindings cursor is empty string’
• Backport of “Fix duplicated content when copying across blob viewer chunks”
• Fix flaky quick_action_suggestions frame-guard spec
• Add siphon-tables image bundling Siphon CDC table definitions
• [19.1] CI: Only set gitlab.com credential helper on gitlab.com
• Revert to jemalloc 5.3.0 (19-1-stable backport)
• Bump CI image

19.0.6

• Backport of ‘Add postgres_index_bloat_estimate SQL function’
• Backport to 19.0: Release note CI job fixes: Skip label + MR pipelines only
• Backport !247590 to 19.0: Fix pipeline test report timeout on large pipelines
• Backport !241962 to 19.0: Make Ci::JobDefinition config size limit configurable - Fix failing pipelines when job config over 1 MiB
• Fix flaky transfer project and quick_action_suggestions frame-guard specs
• [19.0] Remove project_id FKs from two Geo verification state tables
• [19.0] CI: Only set gitlab.com credential helper on gitlab.com

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.2.2
• 19.0.6

Post-deploy migrations

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

• 19.2.2

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.

Original source

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.

Original source

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

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

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.1

CVSS 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.1

CVSS 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.1

CVSS 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.1

CVSS 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.1

CVSS 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.1

CVSS 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.1

CVSS 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.1

CVSS 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.1

CVSS 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.1

CVSS 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.1

CVSS 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.1

CVSS 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.1

CVSS 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
• Backport of “Fix blob preview diff hiding blank added lines”
• Fix nil error when checking checkpoints that are not fully instantiated (19-1 backport)
• Backport of ‘Fix commit list date grouping to use committedDate’
• Backport of ‘Backfill duo_secret_detection_fp_enabled to false’
• Backport of “Add label to skip release note category validation”
• Backport of ‘Fix missing source code in inline blame for legacy file types’
• Backport of “Added a note about ci/cd analytics”
• Backport of “Handle claim conflict when creating placeholder users”
• Backport of “E2E: Perform first time onboarding via UI if presented for E2E tests” into 19.1
• Backport of ‘Fix keys.organization_id NOT NULL constraint failure on Self-Managed/Dedicated upgrades’ to 19.1
• Backport of “Fix self-hosted DWS TLS setting ignored in flow validation and metadata”
• [19.1] Backport of ‘Update net-imap to v0.6.4.1’
• Stop validating web_hook_logs_daily sharding key constraint (19.1 backport)
• Backport 19.1 of “Fix infinite retry on detected language rename”
• Backport ‘Clean up orphan indices in elastic test teardown’ (19.1)
• [19.1] Backport of “Remove –unlink-first and –recursive-unlink from tar extract”
• Backport of ‘Fix approval rule editing locked by non-instance settings’
• 19.1 backport of feat(danger): Block post-deploy migrations on security MRs
• [19.1] Enable LFK cleanup LATERAL join by default
• [19.1] Delete orphaned caches in helm metadata cache backfill
• Backport of ‘Fix self-managed admin/owner cannot enroll namespaces into Orbit’
• Merge branch ‘ramereth/9940-selinux-fcontext-equivalence-el10’ into ‘19-1-stable’
• [19.1 Backport] Bump PostgreSQL to 17.10
• Merge branch ‘renovate/openssl-openssl-3.x’ into ‘19-1-stable’
• 19.1 Backport: Merge branch ‘add-retry-to-manifest-upload’ into ‘master’
• Bump gitlab-omnibus-builder version to 5.60.2
• [19.1] Backport of ‘Uninstall the default net-imap gem shipped with Ruby’
• [19.1] CI: Authenticate gitlab.com clones via GIT_CONFIG_GLOBAL file

19.0.5

• Update gitlab-logger to v4.0.1 (19-0-stable)
• Backport of “Allow AIGW timeout setting on GitLab Dedicated instances”
• Backport of ‘Keep virtual registry settings toggle visible when disabled’ into 19.0
• Backport of “Fix blob preview diff hiding blank added lines”
• Backport of ‘Backfill duo_secret_detection_fp_enabled to false’
• Fix nil error when checking checkpoints that are not fully instantiated (19-0 backport)
• Backport of ‘Fix keys.organization_id NOT NULL constraint failure on Self-Managed/Dedicated upgrades’ to 19.0
• [19.0] Backport of ‘Update net-imap to v0.6.4.1’
• [19.0] Backport of “Remove –unlink-first and –recursive-unlink from tar extract”
• Stop validating web_hook_logs_daily sharding key constraint (19.0 backport)
• Backport ‘Clean up orphan indices in elastic test teardown’ (19.0)
• Backport of ‘Fix approval rule editing locked by non-instance settings’
• 19.0 backport of feat (danger): Block post-deploy migrations on security MR
• Backport of “Remove GIT_CONFIG_GLOBAL=/dev/null from Duo Workflow git hardening”
• [19.0] Rewrite LFK cleanup query as LATERAL join
• [19.0] Delete orphaned caches in helm metadata cache backfill
• Backport 19.0 of “Fix infinite retry on detected language rename”
• Backport of ‘Fix self-managed admin/owner cannot enroll namespaces into Orbit’
• Merge branch ‘ramereth/9940-selinux-fcontext-equivalence-el10’ into ‘19-0-stable’
• [19.0 Backport] Bump PostgreSQL to 17.10
• 19.0 Backport: Merge branch ‘add-retry-to-manifest-upload’ into ‘master’
• Bump gitlab-omnibus-builder version to 5.57.2
• [19.0] Backport of ‘Uninstall the default net-imap gem shipped with Ruby’
• [19.0] CI: Authenticate gitlab.com clones via GIT_CONFIG_GLOBAL file

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.2.1
• 19.1.3
• 19.0.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.

Original source

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.

Previously, the GitLab MCP server and Agent Platform shared the same on and off setting, so you could not turn the MCP server on without also turning on Agent Platform features.

Now you can let other tools access GitLab as an MCP server without turning on the Agent Platform, or keep the GitLab MCP server turned off while you use Agent Platform features.

Automatic rebase before merge

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, if your project used the semi-linear or fast-forward merge method, you had to complete an additional step when the source branch fell behind the target branch.

To merge, you had to select Rebase, wait for it to complete, then return to the merge request to select Merge. That two-step handoff added friction to every merge.

You can now select Enable automatic rebase prior to merge in your project’s merge request settings.

When the setting is on, GitLab rebases the source branch onto the target branch at merge time and you can merge with a single action.

If it’s important to preserve GPG signatures on individual commits, you can leave the setting off.

Code Review Flow for GitLab Duo Enterprise seats

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, when users with GitLab Duo Enterprise seats requested a code review from GitLab Duo, GitLab Duo Code Review would complete the review.

This would occur even if Code Review Flow was turned on for the group. There was no way to turn on the agentic flow for all users.

Now, top-level group Owners can change this default and configure all code reviews to use Code Review Flow instead, regardless of the user’s seat. All reviews will consume GitLab Credits.

This change gives users with GitLab Duo Enterprise seats the same repository-wide context awareness, multi-step reasoning, and review sessions as everyone else.

Exclude merge requests from automatic code reviews (Beta)

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, when automatic reviews were turned on for a project or group, GitLab Duo reviewed every eligible merge request. This included bot-authored dependency updates, feature branches, and experimental work, not just changes the team actually wanted feedback on.

You can now exclude specific merge requests from automatic reviews using exclusion rules. Define a .gitlab/duo/mr-review-automated-rules.yaml file for a project or group, with exclusion rules based on the author, source branch, or target branch. Rules support glob patterns like dependabot/* or *-bot.

You can still request a review manually for any excluded merge request.

This feature is in beta and is gated behind the duo_code_review_automated_rules feature flag, enabled by default.

GitLab MCP server is now available for Free users

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

You can now use the GitLab MCP server without a paid subscription, making it easier than ever to connect your AI tools and agents to GitLab regardless of your plan. This means you get seamless, AI-powered automation and integration capabilities right out of the box, with no subscription upgrade required.

Instance-level custom review instructions

Tier: Premium, Ultimate
Offering: GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

In previous versions of GitLab, you could only define custom review instructions for GitLab Duo at the project or group level.

Administrators who wanted consistent review guidance across an entire instance, such as security rules or internal coding standards, had to duplicate the same instructions in every project.

Now you can configure custom review instructions for an entire instance.

As an administrator, select a project in your instance to use as a template. When GitLab Duo performs a code review, it combines the instructions from the instance-level .gitlab/duo/mr-review-instructions.yaml file with any group-level and project-level instructions. This gives organizations a single source of truth for instance-wide review standards.

Both Code Review Flow and GitLab Duo Code Review support instance-level custom instructions.

Resolve review discussions with GitLab Duo (Beta)

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.

You had to repeat the cycle for every unresolved discussion, and the context-switch overhead would add up across a busy review.

You can now select Resolve with GitLab Duo on any review discussion.

GitLab Duo reads the review comment and the code around it, implements the change the reviewer described, and commits it to your branch. GitLab Duo then replies to the discussion with a short summary of what changed and why, and resolves the thread for you. You can review the changes and reopen the thread if the fix doesn’t address the comment correctly.

Usage billing checks for GitLab Duo Agent Platform Self-Hosted

Tier: Premium, Ultimate
Offering: GitLab Self-Managed, GitLab Dedicated for Government
Links: Documentation · Related Issue

For GitLab Self-Managed customers using self-hosted models with an online license, the GitLab Duo Health now checks that the GitLab instance can reach the following endpoints:

• Customers Portal
• The AI Gateway
• Duo Workflow Service

Connection to these endpoints is necessary for usage billing.

Previously, if a firewall blocked any of these components, administrators had no indication of connectivity issues until users were unable to use a feature. Administrators can now use this new validation check to diagnose issues and review their firewall allowlist before any disruption to users.

Unified DevOps and Security

CI Expert Agent is now generally available

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

The CI Expert Agent is now generally available. This AI-powered assistant helps you create, debug, and optimize GitLab CI/CD pipelines. It analyzes your repository and provides guidance through your pipeline configuration.

The generally available (GA) release builds on the Beta and design-partner program, and brings the agent to production use with real customer workloads to reduce the barrier to CI/CD adoption in your projects.

The agent integrates with Orbit: when Orbit and its Knowledge Graph are enabled, the agent draws on graph-based code intelligence for more contextual pipeline recommendations. Orbit and the Knowledge Graph are in Beta.

Fix CI/CD Pipeline Flow suggests targeted fixes

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

GitLab Duo’s Fix CI/CD Pipeline Flow now gives you two core improvements:

• When relevant files are already in your merge request diff, you get fixes as code suggestions directly on that merge request.
• The flow classifies pipeline failures before acting, so you get a more targeted diagnosis.

The flow also analyzes child pipeline failures across the full pipeline hierarchy, lets you customize its behavior for your project with an AGENTS.md file, and collapses AI reasoning by default to keep your merge request comments clean.

Share your feedback in the feedback issue.

Disable built-in project templates

Tier: Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

When organizations rely on custom project templates, built-in vendor templates can add noise to the template selection experience and, in some cases, bypass server-side hooks or other repository controls.

Administrators can now disable built-in project templates globally from the Admin area, or at the group level for subgroups. The setting cascades automatically so you do not need to configure it for every group individually. Administrators can enforce the value of the setting to ensure groups or subgroups cannot override it.

Both the instance and group settings are also manageable with the REST and GraphQL APIs.

On GitLab.com, only the group-level setting is available.

Fine-grained PAT permissions generally available

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Fine-grained personal access tokens (PATs) are now generally available. Unlike legacy PATs, which grant access to every project and group you belong to, fine-grained PATs allow you to limit each token to specific resources and actions. This makes it easier to apply the principle of least privilege to automation and integrations, which helps reduce the potential impact of a leaked or compromised token.

To make setup easier, use the Add permissions with Duo feature to choose the correct permissions during token creation. Your existing legacy PATs continue to work as before. For new tokens, GitLab recommends fine-grained PATs so each token is scoped only to the resources and actions it needs.

With the GA release, fine-grained PATs now have complete coverage for REST API endpoints, and coverage for the most commonly used GraphQL types and mutations.

GitLab Flavored Markdown references in personal snippets

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

You can now use GitLab Flavored Markdown (GFM) references with personal snippets in two ways:

• GitLab processes GFM references inside personal snippet descriptions and comments, just like in project snippets and other areas of GitLab.
• You can reference a personal snippet from anywhere GFM is supported, such as comments and issue or merge request descriptions, using the $<id> syntax that already works for project snippets.

Because snippet IDs are unique across personal and project snippets, each ID resolves to a single snippet.

Recognize contributors with GitLab Achievements

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated
Links: Documentation · Related Issue

Previously GitLab had no built-in way to formally recognize team members, customers, and contributors for their work. Efforts often went unacknowledged, and communities lacked a consistent way to celebrate the people who make their projects successful.

You can now create custom achievements at the group level and award them to users for their contributions. Each achievement includes a name, description, and avatar. Awarded users can choose which achievements to display on their profile. Achievements give maintainers a visible way to reward participation and help build stronger, more motivated communities.

Thank you to Niklas van Schrick for your contributions to this feature!

Security manager can configure agentic flows

Tier: Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

Users with the Security Manager role can now configure SAST VR, SAST FP, Secrets FP, and Dependency Scanning VR for projects.

GitLab Runner 19.2

Tier: Free, Premium, Ultimate
Offering: GitLab.com, GitLab Self-Managed, GitLab Dedicated, GitLab Dedicated for Government
Links: Documentation · Related Issue

We’re also releasing GitLab Runner 19.2 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

• GitLab Runner now emits the environment key during the job-complete PUT request
• GitLab Runner now includes a circuit breaker that automatically falls back to Rails when KAS job requests fail consecutively

Bug Fixes

• Secret resolution failures are misclassified as runner_system_failure
• Jobs fail with context deadline exceeded when you update GitLab Runner to 19.1.0
• Jobs fail intermittently with context deadline exceeded in the Docker executor
• Artifact downloads fail when FF_CONCRETE is enabled
• KAS Job Router GetJob latency histogram doesn’t show any data in staging
• Automatic runner token rotation causes Docker Autoscaler executor to prune active instances and fail running jobs

The list of all changes is in the GitLab Runner CHANGELOG.

Scale and Deployments

GitLab Duo reads and responds to reviews in 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 GitLab Duo and MCP-based agents to read merge request review conversations. This gives your AI assistant the full context of reviewer feedback, unresolved threads, and discussion history.

You can ask your agent to summarize review comments, draft responses to feedback, and post replies directly to merge request discussions without ever leaving your workflow.

Hosted runners for GitLab Dedicated are generally available

Tier: Ultimate
Offering: GitLab Dedicated
Links: Documentation · Related Issue

Hosted runners for GitLab Dedicated are now generally available. GitLab provisions, patches, and scales runners for you, within the same security and compliance boundary as your GitLab Dedicated instance.

Key capabilities include:

• AWS EC2 instances in the same region as your GitLab Dedicated instance, running in single-tenant, ephemeral VMs destroyed after each job
• Secure outbound PrivateLink connection to your GitLab instance
• Linux x86-64 and Arm64 runners in five sizes, from small to 2X-large
• 99.9% uptime SLA, calculated separately from your GitLab Dedicated instance SLA, to ensure your workflows remain stable, resilient, and online

You create and manage hosted runners yourself in Switchboard, and pay only for what you use, with usage tracked on the GitLab Credits dashboard. To get started, contact your customer success manager or account representative.

AI Gateway for GitLab Dedicated

Tier: Ultimate
Offering: GitLab Dedicated
Links: Documentation · Related Issue

The AI Gateway for GitLab Dedicated runs in your AWS environment, in the same region as your GitLab Dedicated instance. Inference requests, including code inputs, prompts, and model responses, stay within your network and region. All GitLab Duo Agent Platform inference requests stay in the same audit scope as your GitLab Dedicated instance. The AI Gateway for GitLab Dedicated is enabled by default, with no setup required.

Optionally, you can use Bring Your Own Model (BYOM) to connect to your own cloud-hosted models. You can power GitLab Duo Agent Platform capabilities with the models you choose, in your region, under your access controls.

Original source

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

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

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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.2

CVSS 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.

Original source