What is the CVSS score of CVE-2025-14562?

CVE-2025-14562 has a CVSS 3.1 base score of 3.1 (Low). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N. EPSS exploitation probability: 0.2%.

Is there a public PoC exploit available for CVE-2025-14562?

Yes, a public proof-of-concept exploit is available for CVE-2025-14562. Prioritise patching immediately. EPSS: 0.2%.

Is there a patch available for CVE-2025-14562?

Yes, a patch is available for CVE-2025-14562. Update the affected software to the latest version immediately.

GitLab CE/EE CVE-2025-14562

EUVD-2025-210527 LOW

Incorrect Authorization (CWE-863)

2026-07-29 GitLab

GHSA-45h8-qrqh-xr5v

Authentication Bypass Gitlab

3.1

CVSS 3.1 · Vendor: GitLab

Severity by source

Vendor (GitLab) PRIMARY

3.1 LOW

AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

vuln.today AI

3.1 LOW

Requires prior collaborator status on an open MR and subsequent membership removal (AC:H); authenticated developer access mandatory (PR:L); only unauthorized commit capability grants limited integrity impact.

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

4.0 AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (GitLab).

CVSS VectorVendor: GitLab

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 29, 2026 - 20:04 vuln.today

Patch available

Jul 29, 2026 - 20:02 EUVD

CVE Published

Jul 29, 2026 - 19:02 cve.org

LOW 3.1

DescriptionCVE.org

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.

AnalysisAI

GitLab CE/EE permits an authenticated developer-role user who has been removed from a project to continue committing code changes by exploiting improper authorization checks on merge request collaboration settings (CWE-863). The flaw spans a massive version range from 10.6 through 19.2.0, affecting both Community and Enterprise editions. No active exploitation is confirmed via CISA KEV, but a publicly available proof-of-concept exists on HackerOne, and the issue has been patched in 19.0.5, 19.1.3, and 19.2.1.

Technical ContextAI

GitLab CE/EE implements a merge request collaboration feature that grants external contributors or project members commit access to a source branch within the context of a specific merge request. The root cause is CWE-863 (Incorrect Authorization): when a user is removed from project membership, the authorization checks governing merge request collaboration permissions are not properly revoked. The affected CPE is cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:* covering all variants from 10.6 onward. This indicates the collaboration-settings code path lacks a post-removal membership validation step, allowing stale permissions to persist.

RemediationAI

Upgrade GitLab CE/EE to one of the following patched versions: 19.0.5, 19.1.3, or 19.2.1, as confirmed by GitLab's patch release advisory at https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-1-released/. Organizations unable to upgrade immediately should audit active merge requests to identify and manually revoke collaborator access for any users who have been removed from project membership. Additionally, restricting the use of merge request collaboration settings - particularly for projects with frequently rotating contributors or external participants - reduces exposure until a patch is applied. Note that restricting collaboration settings may impact open-source contribution workflows where forked MR collaboration is a standard process.