GitLab Patches 13 Security Flaws (incl. CVE-2026-6267, CVE-2026-12436) Enabling Data Exposure, CI/CD Tampering, and DoS

GitLab Patches 13 Security Flaws (incl. CVE-2026-6267 (TL-2026-1806) is a high-severity software vulnerability scored CVSS 8.5, first published 2026-07-29. It has no confirmed attribution, affects GitLab Inc. GitLab Community Edition (CE), references 13 CVEs (CVE-2026-6267, CVE-2026-12436, CVE-2026-15975), maps to 15 MITRE ATT&CK techniques (T1005, T1053.005, T1059.007), and is covered by 9 detection rules and 24 indicators of compromise.

Key facts for TL-2026-1806

Threat ID
TL-2026-1806
Severity
HIGH
CVSS
8.5 (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H)
Status
PATCHED
Category
VULNERABILITY
First published
2026-07-29
Last reviewed
2026-07-29
Attribution confidence
LOW
Motivation
UNKNOWN
Detection rules
9
Indicators of compromise
24

Malware and tooling in GitLab Patches 13 Security Flaws (incl. CVE-2026-6267

Malware and tooling: GitLab Duo Code Review, GitLab Duo Workflows

GitLab shipped CE/EE 19.2.1, 19.1.3, and 19.0.5 on 2026-07-29, fixing 13 vulnerabilities: a High-severity Workhorse access-control flaw (CVE-2026-6267, CVSS 8.5), a High-severity Pipeline Schedule API mass-assignment flaw enabling CI/CD tampering (CVE-2026-12436, CVSS 8.4), an unauthenticated merge-request-discussion DoS (CVE-2026-15975, CVSS 7.5), and 10 further Medium/Low issues spanning approval-rule race conditions, Virtual Registries credential exposure, project-import authorization gaps, stored XSS, and two Duo AI-feature flaws (prompt injection and governance-policy bypass).

How GitLab Patches 13 Security Flaws (incl. CVE-2026-6267 works

On 2026-07-29 GitLab released Community Edition (CE) and Enterprise Edition (EE) versions 19.2.1, 19.1.3, and 19.0.5, resolving 13 vulnerabilities disclosed together in a single scheduled patch release. GitLab.com (SaaS) and GitLab Dedicated were already running the patched code at release time; the advisory is aimed at self-managed CE/EE administrators, who are strongly urged to upgrade immediately.

The three highest-impact issues are CVE-2026-6267 (CVSS 8.5, CWE-201), an improper access-control flaw in GitLab Workhorse's internal request handling that lets an authenticated Developer-role user retrieve sensitive information beyond their authorization (affects all releases from 10.1.0 up to the patched versions); CVE-2026-12436 (CVSS 8.4, CWE-915), a mass-assignment flaw in the Pipeline Schedule API caused by improper validation of user-supplied attributes, allowing an authenticated low-privilege user to modify CI/CD pipeline-schedule configuration belonging to another user — a direct CI/CD-tampering and software-supply-chain risk (affects 18.0 up to the patched versions); and CVE-2026-15975 (CVSS 7.5, CWE-770), an unauthenticated denial-of-service in merge request discussions caused by insufficient resource throttling, letting an unauthenticated attacker crash or significantly degrade a self-managed instance (affects 11.8 up to the patched versions).

Ten further Medium- and Low-severity issues were fixed in the same release: CVE-2026-13113 (CVSS 6.5, CWE-367, EE-only, affects 17.0+) is a time-of-check/time-of-use race condition in merge-request approval-rule processing that could let a user merge to a protected branch without the required approvals; CVE-2026-16553 (CVSS 5.4, CWE-522, EE-only, affects 18.8+) is an insufficiently-protected-credentials flaw in Virtual Registries (GitLab's upstream package-registry proxy) that could leak credentials meant for a legitimate upstream to an unintended host; CVE-2026-6336 (CVSS 5.3, affects 16.6+) is a missing-authorization flaw exposing project-import source/status information, reported by researcher 3nvz via HackerOne; CVE-2026-14341 (CVSS 4.9, affects 12.8+) is an improper-authorization flaw in a projects API endpoint letting a Maintainer-role user modify protected-branch configuration outside their authorization; CVE-2026-3093 (CVSS 4.7, CWE-79, affects 14.0+) is a stored/reflected cross-site-scripting flaw in paginated list views; CVE-2026-15077 (CVSS 4.3, EE-only, affects 19.1+) is an indirect prompt-injection flaw in GitLab Duo Code Review — the AI code-review assistant trusts untrusted content embedded in code, commit messages, and review artifacts, letting an attacker craft content that redirects the AI backend to disclose data from projects the attacker cannot otherwise access; CVE-2026-15831 (CVSS 4.3, EE-only, affects 19.1+) is a flawed security-token-generation issue in Duo Workflows letting an authenticated user bypass administrator-configured AI tool-governance policies; CVE-2026-14351 (CVSS 4.3, CWE-1230, affects 8.8+) exposes confidential issue titles through merge-request-title-generation metadata; CVE-2026-4672 (CVSS 4.3, affects 18.4+) is an access-control flaw letting a Guest-role user view Pipeline Test Report contents they are not authorized to see, reported by researcher rogerace via HackerOne; and CVE-2025-14562 (CVSS 3.1, affects 10.6+) is an improper-authorization flaw in merge-request collaboration settings that could let a Developer-role user who has been removed from a project retain the ability to commit changes to it.

GitLab's HackerOne public bug-bounty program produced at least four of the reports in this batch, each reserved months before the coordinated July 29 patch release: CVE-2026-4672 (reported by rogerace, reserved 2026-03-23), CVE-2026-6267 (reported by thwin_htet, reserved 2026-04-14), CVE-2026-6336 (reported by 3nvz, reserved 2026-04-15), and CVE-2026-12436 (reported by a0xnirudh, reserved 2026-06-16). GitLab's standard security-release policy publishes full issue-tracker detail for each vulnerability 90 days after the release that patched it, so remaining technical detail on all 13 issues is scheduled to become public around 2026-10-27. As of the hunt/research window, no public proof-of-concept exploit code has been published for any of the 13 CVEs, and none appear in the CISA Known Exploited Vulnerabilities (KEV) catalog — there is no evidence of active in-the-wild exploitation. The cluster is notable for including GitLab's second and third publicly disclosed weaknesses in its Duo AI feature set (prompt injection and AI-governance-policy bypass), reflecting a growing class of AI-assistant-specific vulnerabilities layered on top of traditional web-application access-control and mass-assignment bug classes in the same DevOps platform.

MITRE ATT&CK techniques used in TL-2026-1806

Collection

T1005 Data from Local System; T1213 Data from Information Repositories

Persistence

T1053.005 Scheduled Task; T1098 Account Manipulation

Execution

T1059.007 JavaScript

Initial Access

T1078 Valid Accounts; T1190 Exploit Public-Facing Application; T1195.002 Compromise Software Supply Chain

Privilege Escalation

T1078.004 Cloud Accounts; T1548 Abuse Elevation Control Mechanism

Impact

T1499.003 Application Exhaustion Flood

Discovery

T1518 Software Discovery

Credential Access

T1552 Unsecured Credentials

Exfiltration

T1567 Exfiltration Over Web Service

defense-impairment

T1685 Disable or Modify Tools

Affected products and versions in GitLab Patches 13 Security Flaws (incl. CVE-2026-6267

  • GitLab Inc. — GitLab Community Edition (CE)
    Vulnerable versions: 10.1.0-19.0.4; 19.1.0-19.1.2; 19.2.0
    Fixed in: 19.0.5; 19.1.3; 19.2.1
  • GitLab Inc. — GitLab Enterprise Edition (EE)
    Vulnerable versions: 10.1.0-19.0.4; 19.1.0-19.1.2; 19.2.0
    Fixed in: 19.0.5; 19.1.3; 19.2.1

Remediation for GitLab Patches 13 Security Flaws (incl. CVE-2026-6267

Patches

  • GitLab CE/EE 19.2.1
  • GitLab CE/EE 19.1.3
  • GitLab CE/EE 19.0.5

Immediate actions

  • Upgrade all self-managed GitLab CE/EE instances to 19.2.1, 19.1.3, or 19.0.5 (whichever release branch is deployed) immediately
  • Rotate any credentials configured for GitLab Virtual Registries upstream connections that may have been exposed via CVE-2026-16553 prior to patching
  • Audit Pipeline Schedule API activity and recent CI/CD configuration changes for unauthorized modification consistent with CVE-2026-12436
  • Review Duo Workflows tool-governance policy logs for evidence of bypass consistent with CVE-2026-15831 prior to patching
  • Confirm GitLab.com/GitLab Dedicated tenancy is on the patched build (GitLab stated SaaS/Dedicated customers do not need to take action)

Workarounds

  • No official interim workaround was published by GitLab for any of the 13 CVEs; upgrading to a patched release is the only documented remediation

Longer-term hardening

  • Subscribe to GitLab security release announcements and patch self-managed instances within GitLab's recommended SLA
  • Apply least-privilege review to Developer- and Guest-role assignments, since CVE-2026-6267, CVE-2026-12436, CVE-2026-4672, and CVE-2026-16553 each required only Developer/Guest-level authenticated access
  • Establish a trust-boundary and content-sanitization review process for AI-assisted features (Duo Code Review, Duo Workflows) given the prompt-injection (CVE-2026-15077) and AI-governance-bypass (CVE-2026-15831) findings in this release
  • Enable monitoring/alerting on merge-request-discussion request volume and pipeline-schedule mutation rate to detect resource-exhaustion or CI/CD-tampering attempts resembling CVE-2026-15975 / CVE-2026-12436
  • Re-verify protected-branch configuration and merge-request-collaboration settings after upgrade to rule out residual unauthorized changes made via CVE-2026-14341 or CVE-2025-14562 before the patch was applied
  • Watch GitLab's issue tracker around 2026-10-27 (the scheduled 90-day post-release disclosure date) for additional technical detail on all 13 CVEs that may refine detection or hunting priorities

CVEs associated with GitLab Patches 13 Security Flaws (incl. CVE-2026-6267

  • CVE-2026-6267
  • CVE-2026-12436
  • CVE-2026-15975
  • CVE-2026-13113
  • CVE-2026-16553
  • CVE-2026-6336
  • CVE-2026-14341
  • CVE-2026-3093
  • CVE-2026-15077
  • CVE-2026-15831
  • CVE-2026-14351
  • CVE-2026-4672
  • CVE-2025-14562

Weaknesses (CWE) in GitLab Patches 13 Security Flaws (incl. CVE-2026-6267

CWE-201, CWE-915, CWE-770, CWE-367, CWE-522, CWE-79, CWE-1230

Timeline of GitLab Patches 13 Security Flaws (incl. CVE-2026-6267

  • Security researcher rogerace reported the Guest-role Pipeline Test Report access-control bypass through GitLab's HackerOne bug bounty program; CVE-2026-4672 was reserved the same day, making it the earliest-reported issue in this patch batch.
  • Security researcher thwin_htet reported the GitLab Workhorse internal-request-handling access-control flaw through HackerOne; CVE-2026-6267 (the batch's highest-severity issue at CVSS 8.5) was reserved the same day.
  • Security researcher 3nvz reported the missing-authorization flaw in the project-import status/source API through HackerOne; CVE-2026-6336 was reserved the same day.
  • Security researcher a0xnirudh reported the Pipeline Schedule API mass-assignment flaw through HackerOne; CVE-2026-12436 (CVSS 8.4) was reserved the same day.
  • CVE-2026-6267, CVE-2026-12436, CVE-2026-15975, and the other 10 CVEs in the batch were published on NVD/CVE.org coinciding with the patch release.
  • GitLab confirmed GitLab.com (SaaS) was already running the patched build and that GitLab Dedicated customers did not need to take action, leaving self-managed CE/EE instances as the exposure window.
  • GitLab published the patch-release notes and CVE list on docs.gitlab.com and cross-posted the announcement to the GitLab community forum.
  • GitLab released Community Edition and Enterprise Edition versions 19.2.1, 19.1.3, and 19.0.5, fixing all 13 vulnerabilities including CVE-2026-6267 (CVSS 8.5) and CVE-2026-12436 (CVSS 8.4).
  • TL-Intel-Harness ingested the advisory via the GBHackers RSS feed and opened threat TL-2026-1806 for tracking.
  • HKCERT issued a security bulletin ("GitLab Multiple Vulnerabilities") referencing the July 29 GitLab patch release.
  • GBHackers, CybersecurityNews.com, Cyberpress.org, and Cryptika Cybersecurity published independent coverage summarizing the 13-CVE patch release.
  • Under GitLab's standard security-release policy, full issue-tracker technical detail for each of the 13 vulnerabilities is scheduled to become public approximately 90 days after the July 29, 2026 release date.

Sources cited for GitLab Patches 13 Security Flaws (incl. CVE-2026-6267

Threats related to GitLab Patches 13 Security Flaws (incl. CVE-2026-6267

Detection coverage for TL-2026-1806

As of 2026-07-29, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1806 across Splunk SPL, Microsoft KQL and Sigma, covering 24 indicator(s) of compromise. The whole corpus is readable without an account; a free account unlocks full detection query text in Splunk SPL, Microsoft KQL and Sigma; paid tiers add raw indicator values, correlation and the MCP server. Threadlinqs MCP server · View plans.

Threadlinqs Intelligence — Real-Time Threat Detection Platform

[ 0 threats ] [ 0 det ] [ CRIT: 0 ] [ HIGH: 0 ]
// threat_feed
$ sort --newest
Showing all threats

Latest Threats