Security readout for executives and security teams
Plain-English summary
GitLab fixed an authorization flaw in GitLab EE that could let a logged-in user use AI model settings belonging to namespaces they should not control. The issue is high severity because it may expose sensitive AI configuration data and permit limited unauthorized changes, but the sources do not show active exploitation.
Executive priority
Treat as a high-priority patch for affected GitLab EE environments, especially where many internal users have accounts. The issue requires authentication, which reduces initial access risk, but cross-namespace AI settings access can create confidentiality and governance concerns.
Technical view
CVE-2025-13772 is CWE-862 Missing Authorization in GitLab EE. A low-privileged authenticated user could manipulate namespace identifiers in API requests to access and use AI model settings from unauthorized namespaces. Affected ranges are 18.4 before 18.5.5, 18.6 before 18.6.3, and 18.7 before 18.7.1.
Likely exposure
Exposure is limited to GitLab EE deployments in the affected version ranges with authenticated users and AI model settings present. The provided sources do not identify GitLab CE, SaaS-specific exposure, or unauthenticated access.
Exploitation context
The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. Public detail appears limited; the GitLab issue is listed but marked permissions-required, so exploitation specifics are not available from the bundle.
Researcher notes
The vulnerability centers on authorization checks around namespace identifiers in API requests. Available public evidence supports impact and fixed versions but not exploit mechanics. Avoid assuming broader product impact or confirmed abuse without additional vendor disclosure.
Mitigation direction
- Upgrade GitLab EE to 18.5.5, 18.6.3, 18.7.1, or later applicable releases.
- Prioritize internet-accessible or multi-tenant GitLab EE instances first.
- Inventory namespaces using AI model settings and confirm administrative ownership.
- If upgrade timing is constrained, check current GitLab guidance for supported compensating controls.
Validation and detection
- Confirm each GitLab EE instance version is outside the affected ranges.
- Verify AI model settings are only accessible by authorized namespace administrators.
- Review audit or application logs for unexpected AI settings access across namespaces.
- Check Red Hat and GitLab advisories for updated impact or remediation notes.
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-862: 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-13772 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
- High
- CVSS
- 7.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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
2 official scoresWe 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:L/PR:L/UI:N/S:U/C:H/I:L/A:N2.84.2GitLabCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N2.84.2redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Base CVSS 3.1 score
7.1HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-01-09T10:15:50.081Z: Reported to Red Hat.
- 2026-01-09T10:04:06.293Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- GitLab Issue #581268CVE reference, GitLab · issue-tracking, permissions-required
- https://about.gitlab.com/releases/2026/01/07/patch-release-gitlab-18-7-1-released/CVE reference, GitLab
- https://access.redhat.com/security/cve/CVE-2025-13772CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2428224CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-13772.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
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.