# CVE-2025-14562 — GitLab

> As of 2026-07-29, CVE-2025-14562 is a LOW-severity vulnerability in GitLab, CVSS v3.1 3.1, EPSS 0.2% (19.2th percentile). Threadlinqs Intelligence links 1 tracked threat campaign to CVE-2025-14562, 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-2025-14562?

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.6 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 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.

The record classifies CVE-2025-14562 under weakness class [CWE-863](https://intel.threadlinqs.com/cwe/CWE-863). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction. 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:** 3.1 — LOW (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **EPSS (FIRST):** 0.2% probability of exploitation in the next 30 days, higher than 19.2% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 2.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-29

## Is CVE-2025-14562 being exploited?

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

## Affected products and versions

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

## How to fix CVE-2025-14562

No vendor patch reference has been recorded for CVE-2025-14562 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-2025-14562

1 tracked threat in the Threadlinqs corpus references CVE-2025-14562, 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, GitHub Security Advisories. Last verified by Threadlinqs on 2026-10-10.

**Exploit and proof of concept**

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

**Other references**

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

Canonical: https://intel.threadlinqs.com/cve/CVE-2025-14562
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