On August 26, 2026 GitLab shipped a critical patch across three supported branches: 19.3.1, 19.2.5, and 19.1.7. It carries seven security fixes for Community and Enterprise Edition, and gitlab.com already runs the patched code. Everything below comes from GitLab's patch release notes.
The 60-second version
- Critical patch on Aug 26: 19.3.1, 19.2.5, 19.1.7. Self-managed should upgrade; gitlab.com is already patched.
- CVE-2026-7487 (Low): a Reporter who authored an MR could reset its approval rules through a missing authorization check.
- The reason to upgrade quickly is CVE-2026-18252 (High): the Duo Claude agent could run arbitrary commands in a CI context.
- Five more Medium fixes cover denial of service, protected environments, compliance frameworks, and pipeline execution policies.
The merge request approval bypass (CVE-2026-7487)
In GitLab's words, a Reporter-role user authoring a merge request could have "reset merge request approval rules due to improper authorization checks." It is rated Low and affects Enterprise Edition from 13.1 up to the patched 19.1.7, 19.2.5, and 19.3.1. So it is old, and it is narrow: the actor needs a Reporter role and has to be the MR author.
Narrow does not mean irrelevant if approvals are your merge gate. Approval rules are the thing standing between "someone opened an MR" and "it can merge." A bug that lets the author quietly reset those rules on their own change is exactly the kind of review-integrity gap worth patching, even at Low severity. It also pairs conceptually with the external-status-check authorization issue we wrote up in GitLab merge request API security: both are cases where the check you rely on was not enforced the way you assumed.
The reason to upgrade now: CVE-2026-18252 (High)
The approval bug is the review-relevant one, but it is not why this patch is marked critical. That is CVE-2026-18252, rated High: an authenticated developer could have "executed arbitrary commands in a CI context, due to the Claude agent processing configuration from a user-controlled source." Anything that turns user-controlled config into command execution in CI belongs at the top of your upgrade list. If you run GitLab Duo with the Claude agent, treat this one as the deadline.
The remaining five are Medium:
- CVE-2026-77801: an import pipeline denial of service against background job processing, from missing object count limits.
- CVE-2025-10903: a SCIM API denial of service.
- CVE-2026-3035: a protected environments access-control issue.
- CVE-2026-4398: a compliance framework authorization bypass.
- CVE-2026-15387: untrusted data handling in Pipeline Execution Policies.
What to do
Upgrade self-managed instances to 19.3.1, 19.2.5, or 19.1.7, whichever matches your branch. GitLab.com is already on the patched version, so nothing to do there. If you are still on an older 19.x or an 18.x line, this is a security patch, not a feature upgrade, so take the shortest patched version on your branch first and plan the larger jump separately. Our 19.0 upgrade gotchas post covers the sharp edges on the bigger moves, and the earlier GraphQL authorization vulnerability write-up covers the previous critical patch in this same 19.x series.
Full disclosure: we make PRFlow, which surfaces merge request approval status in Slack so a reviewer can see where a change stands without opening GitLab. That does not patch a CVE, and it is no substitute for upgrading, but visible approval state is one more place a reset would be noticed. If you want the detail, here is the GitLab integration.
Bottom line
The headline is the High-severity Duo agent fix, so patch to your branch's 19.3.1, 19.2.5, or 19.1.7 soon. While you are there, note the approval-rules reset: it is Low severity and narrow, but it is the kind of quiet review-integrity bug that is easy to miss in a patch note full of denial-of-service issues. Approvals are only a gate if they hold.