GitLab 已修复 GitLab EE 中的一个问题,该问题影响所有从 17.8 到 19.3.6 之前、19.4 到 19.4.3 之前、以及 19.5 到 19.5.1 之前的版本。在特定条件下,拥有只读权限的已认证用户可能永久删除现有的漏洞记录。此问题源于错误处理过程中不当的清理逻辑,该逻辑未能区分已存在的记录与新创建的记录。
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-15723 | 8.2 HIGH | Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') in Gi |
| CVE-2026-112212 | 7.5 HIGH | Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in GitLab |
| CVE-2026-12664 | 6.8 MEDIUM | Incorrect Authorization in GitLab |
| CVE-2026-16255 | 5.9 MEDIUM | Incorrect Authorization in GitLab |
| CVE-2026-13319 | 4.3 MEDIUM | Authorization Bypass Through User-Controlled Key in GitLab |
| CVE-2026-105777 | 4.3 MEDIUM | Insertion of Sensitive Information Into Sent Data in GitLab |
| CVE-2026-112378 | 4.3 MEDIUM | Use of Less Trusted Source in GitLab |
| CVE-2026-105711 | 3.5 LOW | Use of Cache Containing Sensitive Information in GitLab |
| CVE-2026-14288 | 3.1 LOW | Use of Incorrectly-Resolved Name or Reference in GitLab |
| CVE-2026-103515 | 2.7 LOW | Incorrect Authorization in GitLab |
No comments yet