Security readout for executives and security teams
Plain-English summary
A former project member may retain limited ability to change code after removal. The issue requires prior authentication, developer-level permissions, specific merge request collaboration conditions, and successful exploitation affects integrity only. GitLab rates it low severity, but unauthorized code changes could still matter in sensitive repositories.
Executive priority
Schedule remediation through normal vulnerability-management timelines, accelerating for repositories containing production code, deployment configuration, or other high-value assets. Review recent former-developer activity because the potential business consequence is an unauthorized source-code change despite the low technical severity.
Technical view
CVE-2025-14562 is a CWE-863 incorrect-authorization flaw in GitLab CE/EE. Improper checks on merge request collaboration settings may let a removed developer commit project changes. It affects versions from 10.6 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1. CVSS 3.1 is 3.1: network-accessible, high complexity, low privileges, and low integrity impact.
Likely exposure
Exposure is limited to affected GitLab CE/EE installations where an authenticated developer was removed while relevant merge request collaboration conditions remained. Organizations with frequent contributor turnover, external developers, or sensitive repositories should give review priority to recently removed project members.
Exploitation context
The source bundle includes a technical HackerOne report, but does not establish exploitation in the wild. The CVE is not listed as KEV. Exploitation requires authentication, prior developer-role permissions, and specific conditions, substantially limiting broad opportunistic abuse.
Researcher notes
The authorization failure concerns stale commit capability after project membership removal, not general unauthenticated access. Analysis should focus on membership-removal timing, developer permissions, merge request collaboration state, and subsequent commits. Available evidence does not describe confidentiality loss, availability impact, public exploitation, or additional affected products.
Mitigation direction
- Upgrade affected 19.0 installations to 19.0.5 or later.
- Upgrade affected 19.1 installations to 19.1.3 or later.
- Upgrade affected 19.2 installations to 19.2.1 or later.
- Consult GitLab's patch-release guidance before upgrading older deployments.
Validation and detection
- Inventory GitLab CE/EE versions and compare them with the documented affected ranges.
- Confirm each deployment runs a fixed or later release within its supported branch.
- Review commits associated with removed developers, especially changes made after membership removal.
- Check relevant project membership and merge request collaboration configurations for former contributors.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-863: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-14562 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N1.61.4GitLabVulnerability scoring details
Base CVSS 3.1 score
3.1LowVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- HackerOne Bug Bounty Report #3460445CVE reference, GitLab · technical-description, exploit
- https://gitlab.com/gitlab-org/gitlab/-/work_items/583889CVE reference, GitLab
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-2-1-released/CVE reference, GitLab
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.