GitLab 已修复 GitLab Enterprise Edition (EE) 中的一个安全漏洞,该漏洞影响 19.2 至 19.3.6 之前的所有版本、19.4 至 19.4.3 之前的所有版本,以及 19.5 至 19.5.1 之前的所有版本。当实例管理员对某个组锁定 Duo 可用性时,拥有该组所有者权限的已认证用户仍可重新启用面向第三方服务的 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-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-112326 | 3.1 LOW | Improper Cleanup on Thrown Exception in GitLab |
No comments yet