在 Traefik 2.11.0 至 2.11.58 版本以及 3.0.0 至 3.7.14 版本中,其 NTLM/Kerberos 后端的往返传输器(round tripper)被存储在一个未按 ServersTransport 进行区分的客户端连接槽中,导致一个服务的 TLS 客户端配置被错误地复用于另一个服务的后端。未经身份验证的客户端可通过向某个后端发起 NTLM 或 Negotiate 质询来“武装”该连接槽,随后利用同一持久连接(keep-alive)访问另一个服务,从而绕过该服务的根证书颁发机构(ro
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-114638 | 8.7 HIGH | Traefik v3.7.0 before v3.7.14 Client CA Mix-up via auth-tls-secret Name Collision |
| CVE-2026-114640 | 8.7 HIGH | Traefik v3.7.0 before v3.7.14 mTLS Header Spoofing via Ingress-NGINX HTTP Router |
| CVE-2026-114639 | 8.7 HIGH | Traefik before 2.11.58 and 3.7.14 Authentication Bypass via Negotiate Connection Pool |
| CVE-2026-114635 | 8.7 HIGH | Traefik before v2.11.58 and v3.7.14 SNI Check Bypass via HTTP/2 Scheme |
| CVE-2026-114637 | 8.7 HIGH | Traefik v3.2.0 before v3.7.14 FastProxy NTLM/Negotiate Connection Pool Identity Leak |
| CVE-2026-114636 | 8.7 HIGH | Traefik v3.7.13 Authentication Bypass via ssl-passthrough Ingress HTTP Router |
| CVE-2026-114656 | 7.5 HIGH | Traefik before 2.11.58 and 3.7.13 mTLS Bypass via Negated Host Matcher |
| CVE-2026-114641 | 3.7 LOW | Traefik before 2.11.58 and 3.7.14 Race Condition in NTLM/Kerberos Round Tripper |
No comments yet