# CVE-2026-14341 — GitLab

> As of 2026-07-29, CVE-2026-14341 is a MEDIUM-severity vulnerability in GitLab, CVSS v3.1 4.9, EPSS 0.5% (43.1th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2026-14341, most recently “GitLab Patches 13 Security Flaws (incl. CVE-2026-6267, CVE-2026-12436) Enabling Data Exposure, CI/CD Tampering, and DoS”.

**Last updated:** 2026-07-29

## What is CVE-2026-14341?

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 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.

The record classifies CVE-2026-14341 under weakness class [CWE-862](https://intel.threadlinqs.com/cwe/CWE-862). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs high-privilege credentials, needs no user interaction, and has high impact on integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 102 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 4.9 — MEDIUM (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **EPSS (FIRST):** 0.5% probability of exploitation in the next 30 days, higher than 43.1% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-29

## Is CVE-2026-14341 being exploited?

It currently carries a trending score of 28 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [GitLab](https://intel.threadlinqs.com/vendors/gitlab): GitLab

## How to fix CVE-2026-14341

No vendor patch reference has been recorded for CVE-2026-14341 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-14341

1 tracked threat in the Threadlinqs corpus references CVE-2026-14341, either in the campaign’s CVE list or as an indicator on the campaign record.

- [GitLab Patches 13 Security Flaws (incl. CVE-2026-6267, CVE-2026-12436) Enabling Data Exposure, CI/CD Tampering, and DoS](https://intel.threadlinqs.com/threat/TL-2026-1806) — HIGH · 2026-07-29

## Sources

Enriched from CVE.org, FIRST EPSS. Last verified by Threadlinqs on 2026-10-10.

**Exploit and proof of concept**

- [hackerone.com — technical description](https://hackerone.com/reports/3807593)

**Other references**

- [gitlab.com](https://gitlab.com/gitlab-org/gitlab/-/work_items/604665)
- [docs.gitlab.com](https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-1-released/)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-14341
Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Sign up free (Blue): https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp