Authorization Bypass Through User-Controlled Key in GitLab (CVE-2026-4398) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-4398

Authorization Bypass Through User-Controlled Key in GitLab

Answer in brief

CVE-2026-4398 records a Unknown severity vulnerability in Authorization Bypass Through User-Controlled Key in GitLab. The current sources do not mark it as known exploited. The current feed maps GitLab/GitLab (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 27, 2026Updated Aug 27, 2026Source checked Aug 27, 2026First seen by HOL Aug 27, 2026Material review Aug 27, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps GitLab/GitLab (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
GitLab/GitLabgeneric	>=18.3 <19.1.7 \|\| >=19.2 <19.2.5 \|\| >=19.3 <19.3.1	19.1.7, 19.2.5, 19.3.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for GitLab/GitLab.
Review the reported fix. Update GitLab/GitLab to 19.1.7 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 27, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 27, 2026

Sources and claim methodology

Upstream source description

GitLab has remediated an issue in GitLab EE affecting all versions from 18.3 before 19.1.7, 19.2 before 19.2.5, and 19.3 before 19.3.1 that, under certain conditions, an authenticated user could have assigned compliance frameworks from namespaces they were not authorized to access to their own project, due to missing namespace validation on self-managed instances.

Quoted source text, attributed separately from HOL analysis.