🛡️ CVE-2025-5846 — gitlab
Description
Missing Authorization in GitLab
An issue has been discovered in GitLab EE affecting all versions from 16.10 before 17.11.5, 18.0 before 18.0.3, and 18.1 before 18.1.1 that could have allowed authenticated users to assign unrelated compliance frameworks to projects by sending crafted GraphQL mutations that bypassed framework-specific permission checks.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs administrative privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity low, availability none.
Weakness class
CVE-2025-5846 is classified as CWE-862: Missing Authorization. No authorisation check is performed before carrying out a restricted action.
Affected software
CVE-2025-5846 is recorded against 1 package.
- gitlab
Timeline and source
Published on 30 June 2025 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
CVE-2025-5846 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| gitlab | — | — |
References
Similar Threats
- High CVE-2020-10073
- Critical CVE-2020-10074
- Medium CVE-2020-10075
- Medium CVE-2020-10076
- Critical CVE-2020-10077
Vulnerability Monitoring
Track new vulnerabilities in gitlab
CVE-2025-5846 is rated CVSS 5.0 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.