GitLab 已修复 GitLab 企业版(EE)中的一个安全漏洞,该漏洞影响所有 17.8 至 19.3.6 之前的版本、19.4 至 19.4.3 之前的版本,以及 19.5 至 19.5.1 之前的版本。在特定条件下,该漏洞可能允许已认证用户绕过有效的订阅验证,访问付费 AI 功能,其根源在于计费资格检查中缺乏充分的服务器端验证。
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-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-112326 | 3.1 LOW | Improper Cleanup on Thrown Exception in GitLab |
| CVE-2026-103515 | 2.7 LOW | Incorrect Authorization in GitLab |
No comments yet