Unauthorized framework assignment via missing namespace validation
Published Aug 27, 2026 · Updated Aug 27, 2026
Authorization bypass in affected GitLab EE releases allows remote authenticated users to assign inaccessible compliance frameworks. The compliance framework assignment path accepts a user-controlled framework identifier without validating that its namespace is authorized for the target project. A low-privileged account on a self-managed instance can attach another namespace's framework to its own project, changing compliance metadata and exposing limited framework information.
Summary
What happened
Authorization bypass in affected GitLab EE releases allows remote authenticated users to assign inaccessible compliance frameworks. The compliance framework assignment path accepts a user-controlled framework identifier without validating that its namespace is authorized for the target project. A low-privileged account on a self-managed instance can attach another namespace's framework to its own project, changing compliance metadata and exposing limited framework information.
The record
- CVE
- CVE-2026-4398
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-639, T1565
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 27, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=18.3 <19.1.7
- Affected versionversion=19.2 <19.2.5
- Affected versionversion=19.3 <19.3.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo