GitLab 已修复 GitLab CE/EE 中的一个安全漏洞,该漏洞影响 10.1 至 19.3.6 之前的所有版本、19.4 至 19.4.3 之前的版本,以及 19.5 至 19.5.1 之前的版本。当同时启用 OmniAuth SAML 和 LDAP 自动关联功能时,由于 OmniAuth 身份关联过程中用于 LDAP 邮箱查找的路径存在输入过滤不当的问题,已认证用户可在无需目标用户任何交互的情况下,接管一个由 LDAP 支持的现有账户。
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-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 |
| CVE-2026-103515 | 2.7 LOW | Incorrect Authorization in GitLab |
No comments yet