This report was translated by AI; nobody has reviewed the translation yet. Original language: Slovak.
[TLP:CLEAR] GitLab CE/EE fixes 6 vulnerabilities
With versions 18.6.1, 18.5.3 and 18.4.5, GitLab fixes 6 vulnerabilities in GitLab Community Edition (CE) and Enterprise Edition (EE) [1]. The most serious of them are listed below.
An authenticated remote attacker can exploit improper synchronization in the CI/CD cache, which may lead to privilege escalation [1].
The vulnerability is present in products:
- GitLab Community Edition; >=18.4, <18.4.5; >=18.5, <18.5.3; >=18.6, <18.6.1
- GitLab Enterprise Edition; >=18.4, <18.4.5; >=18.5, <18.5.3; >=18.6, <18.6.1
CVSS: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N
More information:
- CVE-2024-9183 at cve.org, NVD
- CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') at cwe.mitre.org
The vulnerability was publicly disclosed 26. 11. 2025.
An unauthenticated remote attacker can exploit a flaw in JSON input validation and cause a DoS by sending specially crafted requests [1].
The vulnerability is present in products:
- GitLab Community Edition; >=17.10, <18.4.5; >=18.5, <18.5.3; >=18.6, <18.6.1
- GitLab Enterprise Edition; >=17.10, <18.4.5; >=18.5, <18.5.3; >=18.6, <18.6.1
CVSS: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
More information:
- CVE-2025-12571 at cve.org, NVD
- CWE-770: Allocation of Resources Without Limits or Throttling at cwe.mitre.org
The vulnerability was publicly disclosed 26. 11. 2025.
An unauthenticated remote attacker can bypass verification by modifying headers during account registration and improperly add themselves to any organization [1].
The vulnerability is present in products:
- GitLab Community Edition; >=18.3, <18.4.5; >=18.5, <18.5.3; >=18.6, <18.6.1
- GitLab Enterprise Edition; >=18.3, <18.4.5; >=18.5, <18.5.3; >=18.6, <18.6.1
CVSS: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
More information:
- CVE-2025-12653 at cve.org, NVD
- CWE-290: Authentication Bypass by Spoofing at cwe.mitre.org
The vulnerability was publicly disclosed 26. 11. 2025.
By CESNET, z.s.p.o. Henrieta Paločková on 5. 12. 2025.